View AM29LV640MTB_5667758.PDF datasheet online --- IC-ON-LINE

Datasheet File OCR Text:

!"

#

$
%

!" continuity of specifications

"

%
"
%
" continuity of ordering part numbers ! &
'''('"
%
)*+
" for more information * ! " am29lv640mt/b data sheet
advance information this document contains information on a product under development at advanced micro devices. the information is intended to help you evaluate this product. amd reserves the right to change or discontinue work on this proposed product without notice. publication# 26190 rev: c amendment/ +2 issue date: june 12, 2003 refer to amd?s website (www.amd.com) for the latest information. am29lv640mt/b 64 megabit (4 m x 16-bit/8 m x 8-bit) mirrorbit ? 3.0 volt-only boot sector flash memory distinctive characteristics architectural advantages single power supply operation ? 3 v for read, erase, and program operations manufactured on 0.23 m mirrorbit process technology secsi ? (secured silicon) sector region ? 128-word/256-byte sector for permanent, secure identification through an 8-word/16-byte random electronic serial number, accessible through a command sequence ? may be programmed and locked at the factory or by the customer flexible sector architecture ? one hundred twenty-seven 32 kword/64-kbyte sectors ? eight 4 kword/8 kbyte boot sectors compatibility with jedec standards ? provides pinout and software compatibility for single-power supply flash, and superior inadvertent write protection minimum 100,000 erase cycle guarantee per sector 20-year data retention at 125 c performance characteristics high performance ? 90 ns access time ? 25 ns page read times ? 0.5 s typical sector erase time ? 22 s typical effective write buffer word programming time: 16-word/32-byte write buffer reduces overall programming time for multiple-word/byte updates ? 4-word/8-byte page read buffer ? 16-word/32-byte write buffer low power consumption (typical values at 3.0 v, 5 mhz) ? 30 ma typical active read current ? 50 ma typical erase/program current ? 1 a typical standby mode current package options ? 48-pin tsop ? 63-ball fine-pitch bga ? 64-ball fortified bga software & hardware features software features ? program suspend & resume: read other sectors before programming operation is completed ? erase suspend & resume: read/program other sectors before an erase operation is completed ? data# polling & toggle bits provide status ? unlock bypass program command reduces overall multiple-word programming time ? cfi (common flash interface) compliant: allows host system to identify and accommodate multiple flash devices hardware features ? sector group protection: hardware-level method of preventing write operations within a sector group ? temporary sector unprotect: v id -level method of changing code in locked sectors ? wp#/acc input: write protect input (wp#) protects top or bottom two sectors regardless of sector protection settings acc (high voltage) accelerates programming time for higher throughput during system production ? hardware reset input (reset#) resets device ? ready/busy# output (ry/by#) indicates program or erase cycle completion
2am29lv640mt/b june 12, 2003 advance information general description the am29lv640mt/b is a 64 mbit, 3.0 volt single power supply flash memory device organized as 4,194,304 words or 8,388,608 bytes. the device has an 8-bit/16-bit bus and can be programmed either in the host system or in standard eprom programmers. an access time of 90, 100, 110, or 120 ns is available. note that each access time has a specific operating voltage range (v cc ) and an i/o voltage range (v io ), as specified in the product selector guide and the order- ing information sections. the device is offered in a 48-pin tsop, 63-ball fine-pitch bga or 64-ball forti- fied bga package. each device has separate chip en- able (ce#), write enable (we#) and output enable (oe#) controls. each device requires only a single 3.0 volt power supply for both read and write functions. in addition to a v cc input, a high-voltage accelerated program (acc) function provides shorter programming times through increased current on the wp#/acc input. this feature is intended to facilitate factory throughput dur- ing system production, but may also be used in the field if desired. the device is entirely command set compatible with the jedec single-power-supply flash standard . commands are written to the device using standard microprocessor write timing. write cycles also inter- nally latch addresses and data needed for the pro- gramming and erase operations. the sector erase architecture allows memory sec- tors to be erased and reprogrammed without affecting the data contents of other sectors. the device is fully erased when shipped from the factory. device programming and erasure are initiated through command sequences. once a program or erase oper- ation has begun, the host system need only poll the dq7 (data# polling) or dq6 (toggle) status bits or monitor the ready/busy# (ry/by#) output to deter- mine whether the operation is complete. to facilitate programming, an unlock bypass mode reduces com- mand sequence overhead by requiring only two write cycles to program data instead of four. hardware data protection measures include a low v cc detector that automatically inhibits write opera- tions during power transitions. the hardware sector protection feature disables both program and erase operations in any combination of sectors of memory. this can be achieved in-system or via programming equipment. the erase suspend/erase resume feature allows the host system to pause an erase operation in a given sector to read or program any other sector and then complete the erase operation. the program suspend/program resume feature enables the host system to pause a program operation in a given sector to read any other sector and then complete the pro- gram operation. the hardware reset# pin terminates any operation in progress and resets the device, after which it is then ready for a new operation. the reset# pin may be tied to the system reset circuitry. a system reset would thus also reset the device, enabling the host system to read boot-up firmware from the flash memory device. the device reduces power consumption in the standby mode when it detects specific voltage levels on ce# and reset#, or when addresses have been stable for a specified period of time. the write protect (wp#) feature protects the top or bottom two sectors by asserting a logic low on the wp#/acc pin. the protected sector will still be pro- tected even during accelerated programming. the secsi ? (secured silicon) sector provides a 128-word/256-byte area for code or data that can be permanently protected. once this sector is protected, no further changes within the sector can occur. amd mirrorbit flash technology combines years of flash memory manufacturing experience to produce the highest levels of quality, reliability and cost effec- tiveness. the device electrically erases all bits within a sector simultaneously via hot-hole assisted erase. the data is programmed using hot electron injection.
june 12, 2003 am29lv640mt/b 3 advance information mirrorbit 64 mbit device family related documents to download related documents, click on the following links or go to www.amd.com flash memory prod- uct information mirrorbit flash information te c h - nical documentation. mirrorbit? flash memory write buffer programming and page buffer read implementing a common layout for amd mirrorbit and intel strataflash memory devices migrating from single-byte to three-byte device ids amd mirrorbit? white paper device bus sector architecture packages v io ry/by# wp#, acc wp# protection lv065mu x8 uniform (64 kbyte) 48-pin tsop (std. & rev. pinout), 63-ball fbga yes yes acc only no wp# lv640mt/b x8/x16 boot (8 x 8 kbyte at top & bottom) 48-pin tsop, 63-ball fine-pitch bga, 64-ball fortified bga no yes wp#/acc pin 2 x 8 kbyte top or bottom lv640mh/l x8/x16 uniform (64 kbyte) 56-pin tsop (std. & rev. pinout), 64-ball fortified bga yes yes wp#/acc pin 1 x 64 kbyte high or low lv641mh/l x16 uniform (32 kword) 48-pin tsop (std. & rev. pinout) yes no separate wp# and acc pins 1 x 32 kword top or bottom lv640mu x16 uniform (32 kword) 64-ball fortified bga, 63-ball fine-pitch bga yes yes acc only no wp#
4am29lv640mt/b june 12, 2003 advance information table of contents product selector guide . . . . . . . . . . . . . . . . . . . . . 5 block diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 connection diagrams . . . . . . . . . . . . . . . . . . . . . . 6 pin description. . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 ordering information . . . . . . . . . . . . . . . . . . . . . . . 9 device bus operations . . . . . . . . . . . . . . . . . . . . 10 table 1. device bus operations .....................................................10 word/byte configuration ........................................................ 10 requirements for reading array data ................................... 10 page mode read .................................................................... 11 writing commands/command sequences ............................ 11 write buffer ............................................................................. 11 accelerated program operation ............................................. 11 autoselect functions .............................................................. 11 standby mode ........................................................................ 11 automatic sleep mode ........................................................... 12 reset#: hardware reset pin ............................................... 12 output disable mode .............................................................. 12 table 2. am29lv640mt top boot sector architecture ..................12 table 3. am29lv640mb bottom boot sector architecture .............15 autoselect mode..................................................................... 18 table 4. autoselect codes, (high voltage method) .......................18 sector group protection and unprotection ............................. 19 table 5. am29lv640mt top boot sector protection .....................19 table 6. am29lv640mb bottom boot sector protection ................19 write protect (wp#) ................................................................ 20 temporary sector group unprotect ....................................... 20 figure 1. temporary sector group unprotect operation................ 20 figure 2. in-system sector group protect/unprotect algorithms ... 21 secsi (secured silicon) sector flash memory region .......... 22 table 7. secsi sector contents ......................................................22 figure 3. secsi sector protect verify.............................................. 23 hardware data protection ...................................................... 23 low vcc write inhibit ............................................................ 23 write pulse ?glitch? protection ............................................... 23 logical inhibit .......................................................................... 23 power-up write inhibit ............................................................ 23 common flash memory interface (cfi) . . . . . . . 23 table 9. system interface string......................................................24 command definitions . . . . . . . . . . . . . . . . . . . . . 26 reading array data ................................................................ 26 reset command ..................................................................... 27 autoselect command sequence ............................................ 27 enter secsi sector/exit secsi sector command sequence .. 27 word/byte program command sequence ............................. 27 unlock bypass command sequence ..................................... 28 write buffer programming ...................................................... 28 accelerated program .............................................................. 29 figure 4. write buffer programming operation............................... 30 figure 5. program operation .......................................................... 31 program suspend/program resume command sequence ... 31 figure 6. program suspend/program resume............................... 32 chip erase command sequence ........................................... 32 sector erase command sequence ........................................ 32 figure 7. erase operation............................................................... 33 erase suspend/erase resume commands ........................... 33 command definitions ............................................................. 34 table 12. command definitions (x16 mode, byte# = v ih ) ............ 34 table 13. command definitions (x8 mode, byte# = v il )............... 35 write operation status . . . . . . . . . . . . . . . . . . . . . 36 dq7: data# polling ................................................................. 36 figure 8. data# polling algorithm .................................................. 36 ry/by#: ready/busy#............................................................ 37 dq6: toggle bit i .................................................................... 37 figure 9. toggle bit algorithm........................................................ 38 dq2: toggle bit ii ................................................................... 38 reading toggle bits dq6/dq2 ............................................... 38 dq5: exceeded timing limits ................................................ 39 dq3: sector erase timer ....................................................... 39 dq1: write-to-buffer abort ..................................................... 39 table 14. write operation status ................................................... 39 absolute maximum ratings. . . . . . . . . . . . . . . . . 40 figure 10. maximum negative overshoot waveform ................... 40 figure 11. maximum positive overshoot waveform..................... 40 operating ranges . . . . . . . . . . . . . . . . . . . . . . . . . 40 dc characteristics . . . . . . . . . . . . . . . . . . . . . . . . 41 test conditions. . . . . . . . . . . . . . . . . . . . . . . . . . . 42 figure 12. test setup.................................................................... 42 table 15. test specifications ......................................................... 42 key to switching waveforms. . . . . . . . . . . . . . . . 42 figure 13. input waveforms and measurement levels...................................................................... 42 ac characteristics . . . . . . . . . . . . . . . . . . . . . . . . 43 read-only operations ........................................................... 43 figure 14. read operation timings ............................................... 43 figure 15. page read timings ...................................................... 44 hardware reset (reset#) .................................................... 45 figure 16. reset timings............................................................... 45 erase and program operations .............................................. 46 figure 17. program operation timings.......................................... 47 figure 18. accelerated program timing diagram.......................... 47 figure 19. chip/sector erase operation timings .......................... 48 figure 20. data# polling timings (during embedded algorithms). 49 figure 21. toggle bit timings (during embedded algorithms)...... 50 figure 22. dq2 vs. dq6................................................................. 50 temporary sector unprotect .................................................. 51 figure 23. temporary sector group unprotect timing diagram ... 51 figure 24. sector group protect and unprotect timing diagram .. 52 alternate ce# controlled erase and program operations ..... 53 figure 25. alternate ce# controlled write (erase/program) operation timings.......................................................................... 54 erase and programming performance. . . . . . . . 55 latchup characteristics . . . . . . . . . . . . . . . . . . . . 55 tsop pin and bga package capacitance . . . . . 55 data retention. . . . . . . . . . . . . . . . . . . . . . . . . . . . 55 physical dimensions . . . . . . . . . . . . . . . . . . . . . . 56 ts 048?48-pin standard pinout thin small outline package (tsop) ................................................................................... 56 fbe063?63-ball fine-pitch ball grid array ( f bga) 12 x 11 mm package .............................................................. 57 laa064?64-ball fortified ball grid array ( f bga) 13 x 11 mm package .............................................................. 58 revision summary . . . . . . . . . . . . . . . . . . . . . . . . 59
june 12, 2003 am29lv640mt/b 5 advance information product selector guide note: 1. see ?ac characteristics? for full specifications. block diagram part number am29lv640mt/b speed option v cc = 3.0?3.6 v 90r 100r 110r 120r v cc = 2.7?3.6 v 100 110 120 max. access time (ns) 90 100 110 120 max. ce# access time (ns) 90 100 110 120 max. page access time (t pacc ) 25303040 30 40 max. oe# access time (ns) 25 30 30 40 30 40 input/output buffers x-decoder y-decoder chip enable output enable logic erase voltage generator pgm voltage generator timer v cc detector state control command register v cc v ss we# wp#/acc byte# ce# oe# stb stb dq0 ? dq15 (a-1) sector switches ry/by# reset# data latch y-gating cell matrix address latch a21?a0
6am29lv640mt/b june 12, 2003 advance information connection diagrams c2 d2 e2 f2 g2 h2 j2 k2 c3 d3 e3 f3 g3 h3 j3 k3 c4 d4 e4 f4 g4 h4 j4 k4 c5 d5 e5 f5 g5 h5 j5 k5 c6 d6 e6 f6 g6 h6 j6 k6 c7 d7 a7 b7 a8 b8 a1 b1 a2 e7 f7 g7 h7 j7 k7 l7 l8 m7 m8 l1 l2 m1 m2 nc* nc* nc* nc* nc* nc* nc* nc* nc* nc* nc* nc nc nc nc dq15/a-1 v ss byte# a16 a15 a14 a12 a13 dq13 dq6 dq14 dq7 a11 a10 a8 a9 v cc dq4 dq12 dq5 a19 a21 reset# we# dq11 dq3 dq10 dq2 a20 a18 wp#/acc ry/by# dq9 dq1 dq8 dq0 a5 a6 a17 a7 oe# v ss ce# a0 a1 a2 a4 a3 * balls are shorted together via the substrate but not connected to the die. 1 16 2 3 4 5 6 7 8 17 18 19 20 21 22 23 24 9 10 11 12 13 14 15 48 33 47 46 45 44 43 42 41 40 39 38 37 36 35 34 25 32 31 30 29 28 27 26 a15 a18 a14 a13 a12 a11 a10 a9 a8 a19 a20 we# reset# a21 wp#/acc ry/by# a1 a17 a7 a6 a5 a4 a3 a2 a16 dq2 byte# v ss dq15/a-1 dq7 dq14 dq6 dq13 dq9 dq1 dq8 dq0 oe# v ss ce# a0 dq5 dq12 dq4 v cc dq11 dq3 dq10 48-pin standard tsop 63-ball fine-pitch bga (fbga) top view, balls facing down
june 12, 2003 am29lv640mt/b 7 advance information connection diagrams special package handling instructions special handling is required for flash memory products in molded packages (tsop and bga). the package and/or data integrity may be compromised if the package body is exposed to temperatures above 150 c for prolonged periods of time. b3 c3 d3 e3 f3 g3 h3 b4 c4 d4 e4 f4 g4 h4 b5 c5 d5 e5 f5 g5 h5 b6 c6 d6 e6 f6 g6 h6 b7 c7 d7 e7 f7 g7 h7 b8 c8 d8 e8 f8 g8 h8 nc nc nc v ss nc nc nc v ss dq15/a-1 byte# a16 a15 a14 a12 dq6 dq13 dq14 dq7 a11 a10 a8 dq4 v cc dq12 dq5 a19 a21 reset# dq3 dq11 dq10 dq2 a20 a18 wp#/acc dq1 dq9 dq8 dq0 a5 a6 a17 a3 a4 a5 a6 a7 a8 nc a13 a9 we# ry/by# a7 b2 c2 d2 e2 f2 g2 h2 v ss oe# ce# a0 a1 a2 a4 a2 a3 b1 c1 d1 e1 f1 g1 h1 nc nc nc nc nc nc nc a1 nc 64-ball fortified bga ( f bga) top view, balls facing down
8am29lv640mt/b june 12, 2003 advance information pin description a21?a0 = 22 address inputs dq14?dq0 = 15 data inputs/outputs dq15/a-1 = dq15 (data input/output, word mode), a-1 (lsb address input, byte mode) ce# = chip enable input oe# = output enable input we# = write enable input wp#/acc = hardware write protect input/pro- gramming acceleration input reset# = hardware reset pin input ry/by# = ready/busy output byte# = selects 8-bit or 16-bit mode v cc = 3.0 volt-only single power supply (see product selector guide for speed options and voltage supply tolerances) v ss = device ground nc = pin not connected internally logic symbol 22 16 or 8 dq15?dq0 (a-1) a21?a0 ce# oe# we# reset# ry/by# wp#/acc byte#
june 12, 2003 am29lv640mt/b 9 advance information ordering information standard products amd standard products are available in several packages and o perating ranges. the order numb er (valid combination) is formed by a combination of the following: valid combinations valid combinations list configurat ions planned to be supported in vol- ume for this device. consult the local amd sales office to confirm availability of specific valid combinations and to check on newly re- leased combinations. am29lv640m t 120r pc i temperature range i = industrial (?40 c to +85 c) package type e = 48-pin thin small outline package (tsop) standard pinout (ts 048) pc = 64-ball fortified ball grid array 1.0 mm pitch, 13 x 11 mm package (laa064) wh = 63-ball fine pitch ball grid array 0.80 mm pitch, 12 x 11 mm package (fbe063) speed option see product selector guide and valid combinations sector architecture and wp# protection (wp# = v il ) t = top boot sector device, top two address sectors protected b = bottom boot sector device, bottom two address sectors protected device number/description am29lv640mt/b 64 megabit (4 m x 16-bit/8 m x 8-bit) mirrorbit ? boot sector flash memory 3.0 volt-only read, program, and erase valid combinations for tsop package speed (ns) v cc range am29lv640mt90r, am29lv640mb90r ei 90 3.0?3.6 v am29lv640mt100, am29lv640mb100 100 2.7?3.6 v am29lv640mt110, am29lv640mb110 110 am29lv640mt120, am29lv640mb120 120 am29lv640mt100r, am29lv640mb100r 100 3.0?3.6 v am29lv640mt110r, am29lv640mb110r 110 am29lv640mt120r, am29lv640mb120r 120 valid combinations for bga packages speed (ns) v cc range order number package marking am29lv640mt90r whi l640mt90ri 90 3.0? 3.6 v pci l640mt90ni am29lv640mb90r whi l640mb90ri pci l640mb90ni am29lv640mt100 whi l640mt10vi 100 2.7? 3.6 v pci l640mt10pi am29lv640mb100 whi l640mb10vi pci l640mb10pi am29lv640mt110 whi l640mt11vi 110 pci l640mt11pi am29lv640mb110 whi l640mb11vi pci l640mb11pi am29lv640mt120 whi l640mt12vi 120 pci l640mt12pi am29lv640mb120 whi l640mb12vi pci l640mb12pi am29lv640mt100r whi l640mt10ri 100 3.0? 3.6 v pci l640mt10ni am29lv640mb100r whi l640mb10ri pci l640mb10ni am29lv640mt110r whi l640mt11ri 110 pci l640mt11ni am29lv640mb110r whi l640mb11ri pci l640mb11ni am29lv640mt120r whi l640mt12ri 120 pci l640mt12ni am29lv640mb120r whi l640mb12ri pci l640mb12ni
10 am29lv640mt/b june 12, 2003 advance information device bus operations this section describes the requirements and use of the device bus operations, which are initiated through the internal command register. the command register itself does not occupy any addressable memory loca- tion. the register is a latch used to store the com- mands, along with the address and data information needed to execute the command. the contents of the register serve as inputs to the internal state machine. the state machine outputs dictate the function of the device. table 1 lists the device bus operations, the in- puts and control levels they require, and the resulting output. the following subsections describe each of these operations in further detail. table 1. device bus operations legend: l = logic low = v il , h = logic high = v ih , v id = 11.5?12.5 v, v hh = 11.5?12.5 v, x = don?t care, sa = sector address, a in = address in, d in = data in, d out = data out notes: 1. addresses are a21:a0 in word mode; a21:a-1 in byte mode. sector addresses are a21:a12 in both modes. 2. the sector protect and sector unprotect functions may also be implemented via programming equipment. see the ?sector group protection and unprotection? section. 3. if wp# = v il , the first or last sector remains protected. if wp# = v ih , the top two or bottom two sectors will be protected or unprotected as determined by the method described in ?sector group protection and unprotection?. all sectors are unprotected when shipped from the factory (the secsi sector may be factory protected depending on version ordered.) 4. d in or d out as required by command sequence, data polling, or sector protect algorithm (see figure 2). word/byte configuration the byte# pin controls whether the device data i/o pins operate in the byte or word configuration. if the byte# pin is set at logic ?1?, the device is in word con- figuration, dq0?dq15 are active and controlled by ce# and oe#. if the byte# pin is set at logic ?0?, the device is in byte configuration, and only data i/o pins dq0?dq7 are active and controlled by ce# and oe#. the data i/o pins dq8?dq14 are tri-stated, and the dq15 pin is used as an input for the lsb (a-1) address function. requirements for re ading array data to read array data from the outputs, the system must drive the ce# and oe# pins to v il . ce# is the power control and selects the device. oe# is the output con- trol and gates array data to the output pins. we# should remain at v ih . operation ce# oe# we# reset# wp# acc addresses (note 2) dq0? dq7 dq8?dq15 byte# = v ih byte# = v il read l l h h xx a in d out d out dq8?dq14 = high-z, dq15 = a-1 write (program/erase) l h l h (note 3) x a in (note 4) (note 4) accelerated program l h l h (note 3) v hh a in (note 4) (note 4) standby v cc 0.3 v xx v cc 0.3 v xh x high-z high-z high-z output disable l h h h xx x high-z high-z high-z reset x x x l xx x high-z high-z high-z sector group protect (note 2) lhl v id hx sa, a6 =l, a3=l, a2=l, a1=h, a0=l (note 4) x x sector group unprotect (note 2) lhl v id hx sa, a6=h, a3=l, a2=l, a1=h, a0=l (note 4) x x temporary sector group unprotect xxx v id hx a in (note 4) (note 4) high-z
june 12, 2003 am29lv640mt/b 11 advance information the internal state machine is set for reading array data upon device power-up, or after a hardware reset. this ensures that no spurious alteration of the memory content occurs during the power transition. no com- mand is necessary in this mode to obtain array data. standard microprocessor read cycles that assert valid addresses on the device address inputs produce valid data on the device data outputs. the device remains enabled for read access until the command register contents are altered. see ?reading array data? for more information. refer to the ac read-only operations table for timing spec- ifications and to figure 14 for the timing diagram. refer to the dc characteristics table for the active current specification on reading array data. page mode read the device is capable of fast page mode read and is compatible with the page mode mask rom read oper- ation. this mode provides faster read access speed for random locations within a page. the page size of the device is 4 words/8 bytes. the appropriate page is selected by the higher address bits a(max)?a2. ad- dress bits a1?a0 in word mode (a1?a-1 in byte mode) determine the specific word within a page. this is an asynchronous operation; the microprocessor supplies the specific word location. the random or initial page access is equal to t acc or t ce and subsequent page read accesses (as long as the locations specified by the microprocessor falls within that page) is equivalent to t pacc . when ce# is deasserted and reasserted for a subsequent access, the access time is t acc or t ce . fast page mode ac- cesses are obtained by keeping the ?read-page ad- dresses? constant and changing the ?intra-read page? addresses. writing commands/command sequences to write a command or command sequence (which in- cludes programming data to the device and erasing sectors of memory), the system must drive we# and ce# to v il , and oe# to v ih . the device features an unlock bypass mode to facil- itate faster programming. once the device enters the unlock bypass mode, only two write cycles are re- quired to program a word or byte, instead of four. the ?word/byte program command sequence? section has details on programming data to the device using both standard and unlock bypass command se- quences. an erase operation can erase one sector, multiple sec- tors, or the entire device. tables 3 and 2 indicates the address space that each sector occupies. refer to the dc characteristics table for the active current specification for the write mode. the ac char- acteristics section contains timing specification tables and timing diagrams for write operations. write buffer write buffer programming allows the system to write a maximum of 16 words/32 bytes in one programming operation. this results in faster effective programming time than the standard programming algorithms. see ?write buffer? for more information. accelerated program operation the device offers accelerated program operations through the acc function. this is one of two functions provided by the wp#/acc pin. this function is prima- rily intended to allow faster manufacturing throughput at the factory. if the system asserts v hh on this pin, the device auto- matically enters the aforementioned unlock bypass mode, temporarily unprotects any protected sectors, and uses the higher voltage on the pin to reduce the time required for program operations. the system would use a two-cycle program command sequence as required by the unlock bypass mode. removing v hh from the wp#/acc pin returns the device to nor- mal operation. note that the wp#/acc pin must not be at v hh for operations other than accelerated pro- gramming, or device damage may result. in addition, no external pullup is necessary since the wp#/acc pin has internal pullup to v cc . autoselect functions if the system writes the autoselect command se- quence, the device enters the autoselect mode. the system can then read autoselect codes from the inter- nal register (which is separate from the memory array) on dq7?dq0. standard read cycle timings apply in this mode. refer to the autoselect mode and autose- lect command sequence sections for more informa- tion. standby mode when the system is not reading or writing to the de- vice, it can place the device in the standby mode. in this mode, current consumption is greatly reduced, and the outputs are placed in the high impedance state, independent of the oe# input. the device enters the cmos standby mode when the ce# and reset# pins are both held at v cc 0.3 v. (note that this is a more restricted voltage range than v ih .) if ce# and reset# are held at v ih , but not within v cc 0.3 v, the device will be in the standby mode, but the standby current will be greater. the device re- quires standard access time (t ce ) for read access when the device is in either of these standby modes, before it is ready to read data.
12 am29lv640mt/b june 12, 2003 advance information if the device is deselected during erasure or program- ming, the device draws active current until the operation is completed. refer to the dc characteristics table for the standby current specification. automatic sleep mode the automatic sleep mode minimizes flash device en- ergy consumption. the device automatically enables this mode when addresses remain stable for t acc + 30 ns. the automatic sleep mode is independent of the ce#, we#, and oe# control signals. standard ad- dress access timings provide new data when ad- dresses are changed. while in sleep mode, output data is latched and always available to the system. refer to the dc characteristics table for the automatic sleep mode current specification. reset#: hardware reset pin the reset# pin provides a hardware method of re- setting the device to reading array data. when the re- set# pin is driven low for at least a period of t rp , the device immediately term inates any operation in progress, tristates all output pins, and ignores all read/write commands for the duration of the reset# pulse. the device also resets the internal state ma- chine to reading array data. the operation that was in- terrupted should be reinitiated once the device is ready to accept another command sequence, to en- sure data integrity. current is reduced for the duration of the reset# pulse. when reset# is held at v ss 0.3 v, the device draws cmos standby current (i cc4 ). if reset# is held at v il but not within v ss 0.3 v, the standby current will be greater. the reset# pin may be tied to the system reset cir- cuitry. a system reset would thus also reset the flash memory, enabling the system to read the boot-up firm- ware from the flash memory. refer to the ac characteristics tables for reset# pa- rameters and to figure 16 for the timing diagram. output disable mode when the oe# input is at v ih , output from the device is disabled. the output pins are placed in the high impedance state. table 2. am29lv640mt top boot sector architecture sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range sa0 0000000xxx 64/32 000000h?00ffffh 00000h?07fffh sa1 0000001xxx 64/32 010000h?01ffffh 08000h?0ffffh sa2 0000010xxx 64/32 020000h?02ffffh 10000h?17fffh sa3 0000011xxx 64/32 030000h?03ffffh 18000h?1ffffh sa4 0000100xxx 64/32 040000h?04ffffh 20000h?27fffh sa5 0000101xxx 64/32 050000h?05ffffh 28000h?2ffffh sa6 0000110xxx 64/32 060000h?06ffffh 30000h?37fffh sa7 0000111xxx 64/32 070000h?07ffffh 38000h?3ffffh sa8 0001000xxx 64/32 080000h?08ffffh 40000h?47fffh sa9 0001001xxx 64/32 090000h?09ffffh 48000h?4ffffh sa10 0001010xxx 64/32 0a0000h?0affffh 50000h?57fffh sa11 0001011xxx 64/32 0b0000h?0bffffh 58000h?5ffffh sa12 0001100xxx 64/32 0c0000h?0cffffh 60000h?67fffh sa13 0001101xxx 64/32 0d0000h?0dffffh 68000h?6ffffh sa14 0001101xxx 64/32 0e0000h?0effffh 70000h?77fffh sa15 0001111xxx 64/32 0f0000h?0fffffh 78000h?7ffffh sa16 0010000xxx 64/32 100000h?00ffffh 80000h?87fffh sa17 0010001xxx 64/32 110000h?11ffffh 88000h?8ffffh sa18 0010010xxx 64/32 120000h?12ffffh 90000h?97fffh sa19 0010011xxx 64/32 130000h?13ffffh 98000h?9ffffh sa20 0010100xxx 64/32 140000h?14ffffh a0000h?a7fffh sa21 0010101xxx 64/32 150000h?15ffffh a8000h?affffh sa22 0010110xxx 64/32 160000h?16ffffh b0000h?b7fffh sa23 0010111xxx 64/32 170000h?17ffffh b8000h?bffffh sa24 0011000xxx 64/32 180000h?18ffffh c0000h?c7fffh sa25 0011001xxx 64/32 190000h?19ffffh c8000h?cffffh sa26 0011010xxx 64/32 1a0000h?1affffh d0000h?d7fffh sa27 0011011xxx 64/32 1b0000h?1bffffh d8000h?dffffh
june 12, 2003 am29lv640mt/b 13 advance information sa28 0011000xxx 64/32 1c0000h?1cffffh e0000h?e7fffh sa29 0011101xxx 64/32 1d0000h?1dffffh e8000h?effffh sa30 0011110xxx 64/32 1e0000h?1effffh f0000h?f7fffh sa31 0011111xxx 64/32 1f000 0h?1fffffh f8000h?fffffh sa32 0100000xxx 64/32 200000h?20ffffh f9000h?107fffh sa33 0100001xxx 64/32 210000h?21ffffh 108000h?10ffffh sa34 0100010xxx 64/32 220000h?22ffffh 110000h?117fffh sa35 0101011xxx 64/32 230000h?23ffffh 118000h?11ffffh sa36 0100100xxx 64/32 240000h?24ffffh 120000h?127fffh sa37 0100101xxx 64/32 250000h?25ffffh 128000h?12ffffh sa38 0100110xxx 64/32 260000h?26ffffh 130000h?137fffh sa39 0100111xxx 64/32 270000h?27ffffh 138000h?13ffffh sa40 0101000xxx 64/32 280000h?28ffffh 140000h?147fffh sa41 0101001xxx 64/32 290000h?29ffffh 148000h?14ffffh sa42 0101010xxx 64/32 2a0000h?2affffh 150000h?157fffh sa43 0101011xxx 64/32 2b0000h?2bffffh 158000h?15ffffh sa44 0101100xxx 64/32 2c0000h?2cffffh 160000h?167fffh sa45 0101101xxx 64/32 2d0000h?2dffffh 168000h?16ffffh sa46 0101110xxx 64/32 2e0000h?2effffh 170000h?177fffh sa47 0101111xxx 64/32 2f0000h?2fffffh 178000h?17ffffh sa48 0110000xxx 64/32 300000h?30ffffh 180000h?187fffh sa49 0110001xxx 64/32 310000h?31ffffh 188000h?18ffffh sa50 0110010xxx 64/32 320000h?32ffffh 190000h?197fffh sa51 0110011xxx 64/32 330000h?33ffffh 198000h?19ffffh sa52 0100100xxx 64/32 340000h?34ffffh 1a0000h?1a7fffh sa53 0110101xxx 64/32 350000h?35ffffh 1a8000h?1affffh sa54 0110110xxx 64/32 360000h?36ffffh 1b0000h?1b7fffh sa55 0110111xxx 64/32 370000h?37ffffh 1b8000h?1bffffh sa56 0111000xxx 64/32 380000h?38ffffh 1c0000h?1c7fffh sa57 0111001xxx 64/32 390000h?39ffffh 1c8000h?1cffffh sa58 0111010xxx 64/32 3a0000h?3affffh 1d0000h?1d7fffh sa59 0111011xxx 64/32 3b0000h?3bffffh 1d8000h?1dffffh sa60 0111100xxx 64/32 3c0000h?3cffffh 1e0000h?1e7fffh sa61 0111101xxx 64/32 3d0000h?3dffffh 1e8000h?1effffh sa62 0111110xxx 64/32 3e000 0h?3effffh 1f0000h?1f7fffh sa63 0111111xxx 64/32 3f000 0h?3fffffh 1f8000h?1fffffh sa64 1000000xxx 64/32 400000h?40ffffh 200000h?207fffh sa65 1000001xxx 64/32 410000h?41ffffh 208000h?20ffffh sa66 1000010xxx 64/32 420000h?42ffffh 210000h?217fffh sa67 1000011xxx 64/32 430000h?43ffffh 218000h?21ffffh sa68 1000100xxx 64/32 440000h?44ffffh 220000h?227fffh sa69 1000101xxx 64/32 450000h?45ffffh 228000h?22ffffh sa70 1000110xxx 64/32 460000h?46ffffh 230000h?237fffh sa71 1000111xxx 64/32 470000h?47ffffh 238000h?23ffffh sa72 1001000xxx 64/32 480000h?48ffffh 240000h?247fffh sa73 1001001xxx 64/32 490000h?49ffffh 248000h?24ffffh sa74 1001010xxx 64/32 4a0000h?4affffh 250000h?257fffh sa75 1001011xxx 64/32 4b0000h?4bffffh 258000h?25ffffh sa76 1001100xxx 64/32 4c0000h?4cffffh 260000h?267fffh sa77 1001101xxx 64/32 4d0000h?4dffffh 268000h?26ffffh sa78 1001110xxx 64/32 4e0000h?4effffh 270000h?277fffh sa79 1001111xxx 64/32 4f0000h?4fffffh 278000h?27ffffh sa80 1010000xxx 64/32 500000h?50ffffh 280000h?28ffffh sa81 1010001xxx 64/32 510000h?51ffffh 288000h?28ffffh sa82 1010010xxx 64/32 520000h?52ffffh 290000h?297fffh table 2. am29lv640mt top boot sector architecture (continued) sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range
14 am29lv640mt/b june 12, 2003 advance information sa83 1010011xxx 64/32 530000h?53ffffh 298000h?29ffffh sa84 1010100xxx 64/32 540000h?54ffffh 2a0000h?2a7fffh sa85 1010101xxx 64/32 550000h?55ffffh 2a8000h?2affffh sa86 1010110xxx 64/32 560000h?56ffffh 2b0000h?2b7fffh sa87 1010111xxx 64/32 570000h?57ffffh 2b8000h?2bffffh sa88 1011000xxx 64/32 580000h?58ffffh 2c0000h?2c7fffh sa89 1011001xxx 64/32 590000h?59ffffh 2c8000h?2cffffh sa90 1011010xxx 64/32 5a0000h?5affffh 2d0000h?2d7fffh sa91 1011011xxx 64/32 5b0000h?5bffffh 2d8000h?2dffffh sa92 1011100xxx 64/32 5c0000h?5cffffh 2e0000h?2e7fffh sa93 1011101xxx 64/32 5d0000h?5dffffh 2e8000h?2effffh sa94 1011110xxx 64/32 5e0000h?5effffh 2f0000h?2fffffh sa95 1011111xxx 64/32 5f000 0h?5fffffh 2f8000h?2fffffh sa96 1100000xxx 64/32 600000h?60ffffh 300000h?307fffh sa97 1100001xxx 64/32 610000h?61ffffh 308000h?30ffffh sa98 1100010xxx 64/32 620000h?62ffffh 310000h?317fffh sa99 1100011xxx 64/32 630000h?63ffffh 318000h?31ffffh sa100 1100100xxx 64/32 640000h?64ffffh 320000h?327fffh sa101 1100101xxx 64/32 650000h?65ffffh 328000h?32ffffh sa102 1100110xxx 64/32 660000h?66ffffh 330000h?337fffh sa103 1100111xxx 64/32 670000h?67ffffh 338000h?33ffffh sa104 1101000xxx 64/32 680000h?68ffffh 340000h?347fffh sa105 1101001xxx 64/32 690000h?69ffffh 348000h?34ffffh sa106 1101010xxx 64/32 6a0000h?6affffh 350000h?357fffh sa107 1101011xxx 64/32 6b0000h?6bffffh 358000h?35ffffh sa108 1101100xxx 64/32 6c0000h?6cffffh 360000h?367fffh sa109 1101101xxx 64/32 6d0000h?6dffffh 368000h?36ffffh sa110 1101110xxx 64/32 6e0000h?6effffh 370000h?377fffh sa111 1101111xxx 64/32 6f000 0h?6fffffh 378000h?37ffffh sa112 1110000xxx 64/32 700000h?70ffffh 380000h?387fffh sa113 1110001xxx 64/32 710000h?71ffffh 388000h?38ffffh sa114 1110010xxx 64/32 720000h?72ffffh 390000h?397fffh sa115 1110011xxx 64/32 730000h?73ffffh 398000h?39ffffh sa116 1110100xxx 64/32 740000h?74ffffh 3a0000h?3a7fffh sa117 1110101xxx 64/32 750000h?75ffffh 3a8000h?3affffh sa118 1110110xxx 64/32 760000h?76ffffh 3b0000h?3b7fffh sa119 1110111xxx 64/32 770000h?77ffffh 3b8000h?3bffffh sa120 1111 000xxx 64/32 780000h?78ffffh 3c0000h?3c7fffh sa121 1111 001xxx 64/32 790000h?79ffffh 3c8000h?3cffffh sa122 1111 010xxx 64/32 7a0000h?7affffh 3d0000h?3d7fffh sa123 1111011xxx 64/32 7b0000h?7bffffh 3d8000h?3dffffh sa124 1111 100xxx 64/32 7c0000h?7cffffh 3e0000h?3e7fffh sa125 1111 101xxx 64/32 7d0000h?7dffffh 3e8000h?3effffh sa126 1111110xxx 64/32 7e000 0h?7effffh 3f0000h?3f7fffh sa127 111111 1000 8/4 7f0000h?7f1fffh 3f8000h?3f8fffh sa128 111111 1001 8/4 7f2000h?7f3fffh 3f9000h?3f9fffh sa129 111111 1010 8/4 7f4000h?7f5fffh 3fa000h?3fafffh sa130 1111111011 8/4 7f 6000h?7f7fffh 3fb000h?3fbfffh sa131 1111111100 8/4 7f 8000h?7f9fffh 3fc000h?3fcfffh sa132 1111111101 8/4 7fa00 0h?7fbfffh 3fd000h?3fdfffh sa133 1111111110 8/4 7fc 000h?7fdfffh 3fe000h?3fefffh sa134 1111111111 8/4 7fe 000h?7fffffh 3ff000h?3fffffh table 2. am29lv640mt top boot sector architecture (continued) sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range
june 12, 2003 am29lv640mt/b 15 advance information table 3. am29lv640mb bottom boot sector architecture sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range sa0 0000000000 8/4 000000h?001fffh 00000h?00fffh sa1 0000000001 8/4 002000h?003fffh 01000h?01fffh sa2 0000000010 8/4 004000h?005fffh 02000h?02fffh sa3 0000000011 8/4 006000h?007fffh 03000h?03fffh sa4 0000000100 8/4 008000h?009fffh 04000h?04fffh sa5 0000000101 8/4 00a000h?00bfffh 05000h?05fffh sa6 0000000110 8/4 00c000h?00dfffh 06000h?06fffh sa7 0000000111 8/4 00e000h?00fffffh 07000h?07fffh sa8 0000001xxx 64/32 010000h?01ffffh 08000h?0ffffh sa9 0000010xxx 64/32 020000h?02ffffh 10000h?17fffh sa10 0000011xxx 64/32 030000h?03ffffh 18000h?1ffffh sa11 0000100xxx 64/32 040000h?04ffffh 20000h?27fffh sa12 0000101xxx 64/32 050000h?05ffffh 28000h?2ffffh sa13 0000110xxx 64/32 060000h?06ffffh 30000h?37fffh sa14 0000111xxx 64/32 070000h?07ffffh 38000h?3ffffh sa15 0001000xxx 64/32 080000h?08ffffh 40000h?47fffh sa16 0001001xxx 64/32 090000h?09ffffh 48000h?4ffffh sa17 0001010xxx 64/32 0a0000h?0affffh 50000h?57fffh sa18 0001011xxx 64/32 0b0000h?0bffffh 58000h?5ffffh sa19 0001100xxx 64/32 0c0000h?0cffffh 60000h?67fffh sa20 0001101xxx 64/32 0d0000h?0dffffh 68000h?6ffffh sa21 0001101xxx 64/32 0e0000h?0effffh 70000h?77fffh sa22 0001111xxx 64/32 0f0000h?0fffffh 78000h?7ffffh sa23 0010000xxx 64/32 100000h?00ffffh 80000h?87fffh sa24 0010001xxx 64/32 110000h?11ffffh 88000h?8ffffh sa25 0010010xxx 64/32 120000h?12ffffh 90000h?97fffh sa26 0010011xxx 64/32 130000h?13ffffh 98000h?9ffffh sa27 0010100xxx 64/32 140000h?14ffffh a0000h?a7fffh sa28 0010101xxx 64/32 150000h?15ffffh a8000h?affffh sa29 0010110xxx 64/32 160000h?16ffffh b0000h?b7fffh sa30 0010111xxx 64/32 170000h?17ffffh b8000h?bffffh sa31 0011000xxx 64/32 180000h?18ffffh c0000h?c7fffh sa32 0011001xxx 64/32 190000h?19ffffh c8000h?cffffh sa33 0011010xxx 64/32 1a0000h?1affffh d0000h?d7fffh sa34 0011011xxx 64/32 1b0000h?1bffffh d8000h?dffffh sa35 0011000xxx 64/32 1c0000h?1cffffh e0000h?e7fffh sa36 0011101xxx 64/32 1d0000h?1dffffh e8000h?effffh sa37 0011110xxx 64/32 1e0000h?1effffh f0000h?f7fffh sa38 0011111xxx 64/32 1f000 0h?1fffffh f8000h?fffffh sa39 0100000xxx 64/32 200000h?20ffffh f9000h?107fffh sa40 0100001xxx 64/32 210000h?21ffffh 108000h?10ffffh sa41 0100010xxx 64/32 220000h?22ffffh 110000h?117fffh sa42 0101011xxx 64/32 230000h?23ffffh 118000h?11ffffh sa43 0100100xxx 64/32 240000h?24ffffh 120000h?127fffh sa44 0100101xxx 64/32 250000h?25ffffh 128000h?12ffffh sa45 0100110xxx 64/32 260000h?26ffffh 130000h?137fffh sa46 0100111xxx 64/32 270000h?27ffffh 138000h?13ffffh sa47 0101000xxx 64/32 280000h?28ffffh 140000h?147fffh sa48 0101001xxx 64/32 290000h?29ffffh 148000h?14ffffh sa49 0101010xxx 64/32 2a0000h?2affffh 150000h?157fffh sa50 0101011xxx 64/32 2b0000h?2bffffh 158000h?15ffffh sa51 0101100xxx 64/32 2c0000h?2cffffh 160000h?167fffh sa52 0101101xxx 64/32 2d0000h?2dffffh 168000h?16ffffh sa53 0101110xxx 64/32 2e0000h?2effffh 170000h?177fffh
16 am29lv640mt/b june 12, 2003 advance information sa54 0101111xxx 64/32 2f0000h?2fffffh 178000h?17ffffh sa55 0110000xxx 64/32 300000h?30ffffh 180000h?187fffh sa56 0110001xxx 64/32 310000h?31ffffh 188000h?18ffffh sa57 0110010xxx 64/32 320000h?32ffffh 190000h?197fffh sa58 0110011xxx 64/32 330000h?33ffffh 198000h?19ffffh sa59 0100100xxx 64/32 340000h?34ffffh 1a0000h?1a7fffh sa60 0110101xxx 64/32 350000h?35ffffh 1a8000h?1affffh sa61 0110110xxx 64/32 360000h?36ffffh 1b0000h?1b7fffh sa62 0110111xxx 64/32 370000h?37ffffh 1b8000h?1bffffh sa63 0111000xxx 64/32 380000h?38ffffh 1c0000h?1c7fffh sa64 0111001xxx 64/32 390000h?39ffffh 1c8000h?1cffffh sa65 0111010xxx 64/32 3a0000h?3affffh 1d0000h?1d7fffh sa66 0111011xxx 64/32 3b0000h?3bffffh 1d8000h?1dffffh sa67 0111100xxx 64/32 3c0000h?3cffffh 1e0000h?1e7fffh sa68 0111101xxx 64/32 3d0000h?3dffffh 1e8000h?1effffh sa69 0111110xxx 64/32 3e000 0h?3effffh 1f0000h?1f7fffh sa70 0111111xxx 64/32 3f000 0h?3fffffh 1f8000h?1fffffh sa71 1000000xxx 64/32 400000h?40ffffh 200000h?207fffh sa72 1000001xxx 64/32 410000h?41ffffh 208000h?20ffffh sa73 1000010xxx 64/32 420000h?42ffffh 210000h?217fffh sa74 1000011xxx 64/32 430000h?43ffffh 218000h?21ffffh sa75 1000100xxx 64/32 440000h?44ffffh 220000h?227fffh sa76 1000101xxx 64/32 450000h?45ffffh 228000h?22ffffh sa77 1000110xxx 64/32 460000h?46ffffh 230000h?237fffh sa78 1000111xxx 64/32 470000h?47ffffh 238000h?23ffffh sa79 1001000xxx 64/32 480000h?48ffffh 240000h?247fffh sa80 1001001xxx 64/32 490000h?49ffffh 248000h?24ffffh sa81 1001010xxx 64/32 4a0000h?4affffh 250000h?257fffh sa82 1001011xxx 64/32 4b0000h?4bffffh 258000h?25ffffh sa83 1001100xxx 64/32 4c0000h?4cffffh 260000h?267fffh sa84 1001101xxx 64/32 4d0000h?4dffffh 268000h?26ffffh sa85 1001110xxx 64/32 4e0000h?4effffh 270000h?277fffh sa86 1001111xxx 64/32 4f0000h?4fffffh 278000h?27ffffh sa87 1010000xxx 64/32 500000h?50ffffh 280000h?28ffffh sa88 1010001xxx 64/32 510000h?51ffffh 288000h?28ffffh sa89 1010010xxx 64/32 520000h?52ffffh 290000h?297fffh sa90 1010011xxx 64/32 530000h?53ffffh 298000h?29ffffh sa91 1010100xxx 64/32 540000h?54ffffh 2a0000h?2a7fffh sa92 1010101xxx 64/32 550000h?55ffffh 2a8000h?2affffh sa93 1010110xxx 64/32 560000h?56ffffh 2b0000h?2b7fffh sa94 1010111xxx 64/32 570000h?57ffffh 2b8000h?2bffffh sa95 1011000xxx 64/32 580000h?58ffffh 2c0000h?2c7fffh sa96 1011001xxx 64/32 590000h?59ffffh 2c8000h?2cffffh sa97 1011010xxx 64/32 5a0000h?5affffh 2d0000h?2d7fffh sa98 1011011xxx 64/32 5b0000h?5bffffh 2d8000h?2dffffh sa99 1011100xxx 64/32 5c0000h?5cffffh 2e0000h?2e7fffh sa100 1011101xxx 64/32 5d0000h?5dffffh 2e8000h?2effffh sa101 1011110xxx 64/32 5e0000h?5effffh 2f0000h?2fffffh sa102 1011111xxx 64/32 5f000 0h?5fffffh 2f8000h?2fffffh sa103 1100000xxx 64/32 600000h?60ffffh 300000h?307fffh sa104 1100001xxx 64/32 610000h?61ffffh 308000h?30ffffh sa105 1100010xxx 64/32 620000h?62ffffh 310000h?317fffh sa106 1100011xxx 64/32 630000h?63ffffh 318000h?31ffffh sa107 1100100xxx 64/32 640000h?64ffffh 320000h?327fffh sa108 1100101xxx 64/32 650000h?65ffffh 328000h?32ffffh table 3. am29lv640mb bottom boot sector architecture (continued) sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range
june 12, 2003 am29lv640mt/b 17 advance information note: the address range is a21:a-1 in byte mode (byte# = v il ) or a21:a0 in word mode (byte# = v ih ) sa109 1100110xxx 64/32 660000h?66ffffh 330000h?337fffh sa110 1100111xxx 64/32 670000h?67ffffh 338000h?33ffffh sa111 1101000xxx 64/32 680000h?68ffffh 340000h?347fffh sa112 1101001xxx 64/32 690000h?69ffffh 348000h?34ffffh sa113 1101010xxx 64/32 6a0000h?6affffh 350000h?357fffh sa114 1101011xxx 64/32 6b0000h?6bffffh 358000h?35ffffh sa115 1101100xxx 64/32 6c0000h?6cffffh 360000h?367fffh sa116 1101101xxx 64/32 6d0000h?6dffffh 368000h?36ffffh sa117 1101110xxx 64/32 6e0000h?6effffh 370000h?377fffh sa118 1101111xxx 64/32 6f000 0h?6fffffh 378000h?37ffffh sa119 1110000xxx 64/32 700000h?70ffffh 380000h?387fffh sa120 1110001xxx 64/32 710000h?71ffffh 388000h?38ffffh sa121 1110010xxx 64/32 720000h?72ffffh 390000h?397fffh sa122 1110011xxx 64/32 730000h?73ffffh 398000h?39ffffh sa123 1110100xxx 64/32 740000h?74ffffh 3a0000h?3a7fffh sa124 1110101xxx 64/32 750000h?75ffffh 3a8000h?3affffh sa125 1110110xxx 64/32 760000h?76ffffh 3b0000h?3b7fffh sa126 1110111xxx 64/32 770000h?77ffffh 3b8000h?3bffffh sa127 1111 000xxx 64/32 780000h?78ffffh 3c0000h?3c7fffh sa128 1111 001xxx 64/32 790000h?79ffffh 3c8000h?3cffffh sa129 1111 010xxx 64/32 7a0000h?7affffh 3d0000h?3d7fffh sa130 1111011xxx 64/32 7b0000h?7bffffh 3d8000h?3dffffh sa131 1111 100xxx 64/32 7c0000h?7cffffh 3e0000h?3e7fffh sa132 1111 101xxx 64/32 7d0000h?7dffffh 3e8000h?3effffh sa133 1111110xxx 64/32 7e000 0h?7effffh 3f0000h?3f7fffh sa134 111111 1000 64/32 7f0000h?7fffffh 3f8000h?3fffffh table 3. am29lv640mb bottom boot sector architecture (continued) sector sector address a21?a12 sector size (kbytes/kwords) (x8) address range (x16) address range
18 am29lv640mt/b june 12, 2003 advance information autoselect mode the autoselect mode provides manufacturer and de- vice identification, and sect or protection verification, through identifier codes output on dq7?dq0. this mode is primarily intended for programming equip- ment to automatically match a device to be pro- grammed with its corresponding programming algorithm. however, the autoselect codes can also be accessed in-system through the command register. when using programming equipment, the autoselect mode requires v id on address pin a9. address pins a6, a3, a2, a1, and a0 must be as shown in ta b l e 4 . in addition, when verifying sector protection, the sector address must appear on the appropriate highest order address bits (see tables 2 and 3 ). table 4 shows the remaining address bits that are don?t care. when all necessary bits have been set as required, the pro- gramming equipment may then read the correspond- ing identifier code on dq7?dq0. to access the autoselect codes in-system, the host system can issue the autoselect command via the command register, as shown in tables 12 and 13 . this method does not require v id . refer to the autoselect command sequence section for more information. table 4. autoselect codes, (high voltage method) legend: l = logic low = v il , h = logic high = v ih , sa = sector address, x = don?t care. description ce# oe# we# a21 to a15 a14 to a10 a9 a8 to a7 a6 a5 to a4 a3 to a2 a1 a0 dq8 to dq15 dq7 to dq0 byte# = v ih byte# = v il manufacturer id : amd l l h x x v id x l x l l l 00 x 01h device id cycle 1 llhxx v id xl x llh 22 x 7eh cycle 2 h h l 22 x 10h cycle 3 hhh 22 x 00 (bottom boot) 01h (top boot) sector protection verification llhsax v id xl x l h l x x 01h (protected), 00h (unprotected) secsi sector indicator bit (dq7), wp# protects top two address sector llhxx v id xl x l h h x x 98h (factory locked), 18h (not factory locked) secsi sector indicator bit (dq7), wp# protects bottom two address sector llhxx v id xl x l h h x x 88h (factory locked), 08h (not factory locked)
june 12, 2003 am29lv640mt/b 19 advance information sector group protection and unprotection the hardware sector group protection feature disables both program and erase operations in any sector group. in this device, a sector group consists of four adjacent sectors that are protected or unprotected at the same time (see tables 5 and 6 ). the hardware sector group unprotection feature re-enables both pro- gram and erase operations in previously protected sector groups. sector group protection/unprotection can be implemented via two methods. sector protection/unprotection requires v id on the re- set# pin only, and can be implemented either in-sys- tem or via programming equipment. figure 2 shows the algorithms and figure 24 shows the timing dia- gram. this method uses standard microprocessor bus cycle timing. for sector group unprotect, all unpro- tected sector groups must first be protected prior to the first sector group unprotect write cycle. the device is shipped with all sector groups unpro- tected. amd offers the option of programming and protecting sector groups at its factory prior to shipping the device through amd?s expressflash? service. contact an amd representative for details. it is possible to determine whether a sector group is protected or unprotected. see the autoselect mode section for details. table 5. am29lv640mt top boot sector protection sector a21?a12 sector/ sector block size sa0-sa3 00000xxxxx 256 (4x64) kbytes sa4-sa7 00001xxxxx 256 (4x64) kbytes sa8-sa11 00010xxxxx 256 (4x64) kbytes sa12-sa15 00011xxxxx 256 (4x64) kbytes sa16-sa19 00100xxxxx 256 (4x64) kbytes sa20-sa23 00101xxxxx 256 (4x64) kbytes sa24-sa27 00110xxxxx 256 (4x64) kbytes sa28-sa31 00111xxxxx 256 (4x64) kbytes sa32-sa35 01000xxxxx 256 (4x64) kbytes sa36-sa39 01001xxxxx 256 (4x64) kbytes sa40-sa43 01010xxxxx 256 (4x64) kbytes sa44-sa47 01011xxxxx 256 (4x64) kbytes sa48-sa51 01100xxxxx 256 (4x64) kbytes sa52-sa55 01101xxxxx 256 (4x64) kbytes sa56-sa59 01110xxxxx 256 (4x64) kbytes sa60-sa63 01111xxxxx 256 (4x64) kbytes sa64-sa67 10000xxxxx 256 (4x64) kbytes sa68-sa71 10001xxxxx 256 (4x64) kbytes sa72-sa75 10010xxxxx 256 (4x64) kbytes sa76-sa79 10011xxxxx 256 (4x64) kbytes sa80-sa83 10100xxxxx 256 (4x64) kbytes sa84-sa87 10101xxxxx 256 (4x64) kbytes sa88-sa91 10110xxxxx 256 (4x64) kbytes sa92-sa95 10111xxxxx 256 (4x64) kbytes sa96-sa99 11000xxxxx 256 (4x64) kbytes sa100-sa103 11001xxxxx 256 (4x64) kbytes sa104-sa107 11010xxxxx 256 (4x64) kbytes sa108-sa111 11011xxxxx 256 (4x64) kbytes sa112-sa115 11100xxxxx 256 (4x64) kbytes sa116-sa119 11101xxxxx 256 (4x64) kbytes sa120-sa123 11110xxxxx 256 (4x64) kbytes sa124-sa126 1111100xxx 1111101xxx 1111110xxx 192 (3x64) kbytes sa127 111111 1000 8 kbytes sa128 111111 1001 8 kbytes sa129 111111 1010 8 kbytes sa130 1111111011 8 kbytes sa131 1111111100 8 kbytes sa132 1111111101 8 kbytes sa133 1111111110 8 kbytes sa134 1111111111 8 kbytes table 6. am29lv640mb bottom boot sector protection sector a21?a12 sector/ sector block size sa0 0000000000 8 kbytes sa1 0000000001 8 kbytes sa2 0000000010 8 kbytes sa3 0000000011 8 kbytes sa4 0000000100 8 kbytes sa5 0000000101 8 kbytes sa6 0000000110 8 kbytes sa7 0000000111 8 kbytes sa8?sa10 0000001xxx, 0000010xxx, 0000011xxx, 192 (3x64) kbytes sa11?sa14 00001xxxxx 256 (4x64) kbytes sa15?sa18 00010xxxxx 256 (4x64) kbytes sa19?sa22 00011xxxxx 256 (4x64) kbytes sa23?sa26 00100xxxxx 256 (4x64) kbytes sa27-sa30 00101xxxxx 256 (4x64) kbytes sa31-sa34 00110xxxxx 256 (4x64) kbytes sa35-sa38 00111xxxxx 256 (4x64) kbytes sa39-sa42 01000xxxxx 256 (4x64) kbytes sa43-sa46 01001xxxxx 256 (4x64) kbytes sa47-sa50 01010xxxxx 256 (4x64) kbytes sa51-sa54 01011xxxxx 256 (4x64) kbytes sector a21?a12 sector/ sector block size
20 am29lv640mt/b june 12, 2003 advance information write protect (wp#) the write protect function provides a hardware method of protecting the top two or bottom two sectors without using v id . wp# is one of two functions pro- vided by the wp#/acc input. if the system asserts v il on the wp#/acc pin, the de- vice disables program and er ase functions in the first or last sector independently of whether those sectors were protected or unprotected using the method de- scribed in ?sector group protection and unprotection?. note that if wp#/acc is at v il when the device is in the standby mode, the maximum input load current is increased. see the table in ?dc characteristics?. if the system asserts v ih on the wp#/acc pin, the de- vice reverts to whether the top or bottom two sectors were previously set to be protected or unprotected using the method described in ?sector group protec- tion and unprotection?. note: no external pullup is necessary since the wp#/acc pin has internal pullup to v cc temporary sector group unprotect ( note: in this device, a sector group consists of four adjacent sectors that are protected or unprotected at the same time (see table 6 ). this feature allows temporary unprotection of previ- ously protected sector groups to change data in-sys- tem. the sector group unprotect mode is activated by setting the reset# pin to v id . during this mode, for- merly protected sector groups can be programmed or erased by selecting the sector group addresses. once v id is removed from the reset# pin, all the previ- ously protected sector groups are protected again. figure 1 shows the algorithm, and figure 23 shows the timing diagrams, for this feature. figure 1. temporary sector group unprotect operation sa55?sa58 01100xxxxx 256 (4x64) kbytes sa59?sa62 01101xxxxx 256 (4x64) kbytes sa63?sa66 01110xxxxx 256 (4x64) kbytes sa67?sa70 0 1111xxxxx 256 (4x64) kbytes sa71?sa74 10000xxxxx 256 (4x64) kbytes sa75?sa78 10001xxxxx 256 (4x64) kbytes sa79?sa82 10010xxxxx 256 (4x64) kbytes sa83?sa86 10011xxxxx 256 (4x64) kbytes sa87?sa90 10100xxxxx 256 (4x64) kbytes sa91?sa94 10101xxxxx 256 (4x64) kbytes sa95?sa98 10110xxxxx 256 (4x64) kbytes sa99?sa102 10111xxxxx 256 (4x64) kbytes sa103?sa106 11000xxxxx 256 (4x64) kbytes sa107?sa110 11001xxxxx 256 (4x64) kbytes sa111?sa114 11010xxxxx 256 (4x64) kbytes sa115?sa118 11011xxxxx 256 (4x64) kbytes sa119?sa122 11100xxxxx 256 (4x64) kbytes sa123?sa126 11101xxxxx 256 (4x64) kbytes sa127?sa130 11110xxxxx 256 (4x64) kbytes sa131?sa134 1 1111xxxxx 256 (4x64) kbytes table 6. am29lv640mb bottom boot sector protection (continued) sector a21?a12 sector/ sector block size start perform erase or program operations reset# = v ih temporary sector group unprotect completed (note 2) reset# = v id (note 1) notes: 1. all protected sector groups unprotected (if wp# = v il , the first or last sector will remain protected). 2. all previously protected se ctor groups are protected once again.
june 12, 2003 am29lv640mt/b 21 advance information figure 2. in-system sector group protect/unprotect algorithms sector group protect: write 60h to sector group address with a6?a0 = 0xx0010 set up sector group address wait 150 s verify sector group protect: write 40h to sector group address with a6?a0 = 0xx0010 read from sector group address with a6?a0 = 0xx0010 start plscnt = 1 reset# = v id wait 1 s first write cycle = 60h? data = 01h? remove v id from reset# write reset command sector group protect complete yes yes no plscnt = 25? yes device failed increment plscnt temporary sector group unprotect mode no sector group unprotect: write 60h to sector group address with a6?a0 = 1xx0010 set up first sector group address wait 15 ms verify sector group unprotect: write 40h to sector group address with a6?a0 = 1xx0010 read from sector group address with a6?a0 = 1xx0010 start plscnt = 1 reset# = v id wait 1 s data = 00h? last sector group verified? remove v id from reset# write reset command sector group unprotect complete yes no plscnt = 1000? yes device failed increment plscnt temporary sector group unprotect mode no all sector groups protected? yes protect all sector groups: the indicated portion of the sector group protect algorithm must be performed for all unprotected sector groups prior to issuing the first sector group unprotect address set up next sector group address no yes no yes no no yes no sector group protect algorithm sector group unprotect algorithm first write cycle = 60h? protect another sector group? reset plscnt = 1
22 am29lv640mt/b june 12, 2003 advance information secsi (secured silicon) sector flash memory region the secsi (secured silicon) sector feature provides a flash memory region that enables permanent part identification through an electronic serial number (esn). the secsi sector is 128 words/256 bytes in length, and uses a secsi sector indicator bit (dq7) to indicate whether or not the secsi sector is locked when shipped from the factory. this bit is permanently set at the factory and cannot be changed, which pre- vents cloning of a factory locked part. this ensures the security of the esn once the product is shipped to the field. amd offers the device with the secsi sector either factory locked or customer lockable. the fac- tory-locked version is always protected when shipped from the factory, and has the secsi (secured silicon) sector indicator bit permanently set to a ?1.? the cus- tomer-lockable version is shipped with the secsi sec- tor unprotected, allowing customers to program the sector after receiving the device. the customer-lock- able version also has the secsi sector indicator bit permanently set to a ?0.? thus, the secsi sector indi- cator bit prevents customer-lockable devices from being used to replace devices that are factory locked. the secsi sector address space in this device is allo- cated as follows: the system accesses the secsi sector through a command sequence (see ?enter secsi sector/exit secsi sector command sequence?). after the system has written the enter secsi sector command se- quence, it may read the secsi sector by using the ad- dresses normally occupied by the first sector (sa0). this mode of operation continues until the system is- sues the exit secsi sector command sequence, or until power is removed from the device. on power-up, or following a hardware reset, the device reverts to sending commands to sector sa0. note that the acc function and unlock bypass modes are not available when the secsi sector is enabled. factory locked: secsi sector programmed and protected at the factory in devices with an esn, the secsi sector is protected when the device is shipped from the factory. the secsi sector cannot be modified in any way. see table 7 for secsi sector addressing. customers may opt to have their code programmed by amd through the amd expressflash service. the de- vices are then shipped from amd?s factory with the secsi sector permanently locked. contact an amd representative for details on using amd?s express- flash service. customer lockable: secsi sector not programmed or protected at the factory as an alternative to the factory-locked version, the de- vice may be ordered such that the customer may pro- gram and protect the 128-word/256 bytes secsi sector. the system may program the secsi sector using the write-buffer, accelerated and/or unlock bypass meth- ods, in addition to the standard programming com- mand sequence. see command definitions . programming and protecting the secsi sector must be used with caution since, once protected, there is no procedure available for unprotecting the secsi sector area and none of the bits in the secsi sector memory space can be modified in any way. the secsi sector area can be protected using one of the following procedures: write the three-cycle enter secsi sector region command sequence, and then follow the in-system sector protect algorithm as shown in figure 2, ex- cept that reset# may be at either v ih or v id . this allows in-system protection of the secsi sector without raising any device pin to a high voltage. note that this method is only applicable to the secsi sector. to verify the protect/unprotect status of the secsi sector, follow the algorithm shown in figure 3. once the secsi sector is programmed, locked and verified, the system must write the exit secsi sector region command sequence to return to reading and writing within the remainder of the array. table 7. secsi sector contents secsi sector address range standard factory locked expressflash factory locked customer lockable x16 x8 000000h? 000007h 000000h? 00000fh esn esn or determined by customer determined by customer 000008h? 00007fh 000010h? 0000ffh unavailable determined by customer
june 12, 2003 am29lv640mt/b 23 advance information figure 3. secsi sector protect verify hardware data protection the command sequence requirement of unlock cycles for programming or erasing provides data protection against inadvertent writes (refer to tables 12 and 13 for command definitions). in addition, the following hardware data protection measures prevent accidental erasure or programming, which might otherwise be caused by spurious system level signals during v cc power-up and power-down transitions, or from system noise. low v cc write inhibit when v cc is less than v lko , the device does not ac- cept any write cycles. th is protects data during v cc power-up and power-down. the command register and all internal program/erase circuits are disabled, and the device resets to the read mode. subsequent writes are ignored until v cc is greater than v lko . the system must provide the proper signals to the control pins to prevent unintentional writes when v cc is greater than v lko . write pulse ?glitch? protection noise pulses of less than 5 ns (typical) on oe#, ce# or we# do not initiate a write cycle. logical inhibit write cycles are inhibited by holding any one of oe# = v il , ce# = v ih or we# = v ih . to initiate a write cycle, ce# and we# must be a logical zero while oe# is a logical one. power-up write inhibit if we# = ce# = v il and oe# = v ih during power up, the device does not accept commands on the rising edge of we#. the internal state machine is automati- cally reset to the read mode on power-up. common flash memory interface (cfi) the common flash interface (cfi) specification out- lines device and host system software interrogation handshake, which allows specific vendor-specified software algorithms to be used for entire families of devices. software support can then be device-inde- pendent, jedec id-independent, and forward- and backward-compatible for the specified flash device families. flash vendors can standardize their existing interfaces for long-term compatibility. this device enters the cfi query mode when the sys- tem writes the cfi query command, 98h, to address 55h, any time the device is ready to read array data. the system can read cfi information at the addresses given in tables 8 ? 11 . to terminate reading cfi data, the system must write the reset command. the system can also write the cfi query command when the device is in the autoselect mode. the device enters the cfi query mode, and the system can read cfi data at the addresses given in tables 8 ? 11 . the system must write the reset command to return the de- vice to reading array data. for further information, please refer to the cfi specifi- cation and cfi publication 100, available via the world wide web at http://www.amd.com/flash/cfi. al- ternatively, contact an amd representative for copies of these documents. write 60h to any address write 40h to secsi sector address with a6 = 0, a1 = 1, a0 = 0 start reset# = v ih or v id wait 1 s read from secsi sector address with a6 = 0, a1 = 1, a0 = 0 if data = 00h, secsi sector is unprotected. if data = 01h, secsi sector is protected. remove v ih or v id from reset# write reset command secsi sector protect verify complete
24 am29lv640mt/b june 12, 2003 advance information table 8. cfi query identification string table 9. system interface string addresses (x16) addresses (x8) data description 10h 11h 12h 20h 22h 24h 0051h 0052h 0059h query unique ascii string ?qry? 13h 14h 26h 28h 0002h 0000h primary oem command set 15h 16h 2ah 2ch 0040h 0000h address for primary extended table 17h 18h 2eh 30h 0000h 0000h alternate oem command set (00h = none exists) 19h 1ah 32h 34h 0000h 0000h address for alternate oem extended table (00h = none exists) addresses (x16) addresses (x8) data description 1bh 36h 0027h v cc min. (write/erase) d7?d4: volt, d3?d0: 100 millivolt 1ch 38h 0036h v cc max. (write/erase) d7?d4: volt, d3?d0: 100 millivolt 1dh 3ah 0000h v pp min. voltage (00h = no v pp pin present) 1eh 3ch 0000h v pp max. voltage (00h = no v pp pin present) 1fh 3eh 0007h typical timeout per single byte/word write 2 n s 20h 40h 0007h typical timeout for min. size buffer write 2 n s (00h = not supported) 21h 42h 000ah typical timeout per individual block erase 2 n ms 22h 44h 0000h typical timeout for full chip erase 2 n ms (00h = not supported) 23h 46h 0001h max. timeout for byte/word write 2 n times typical 24h 48h 0005h max. timeout for buffer write 2 n times typical 25h 4ah 0004h max. timeout per individual block erase 2 n times typical 26h 4ch 0000h max. timeout for full chip erase 2 n times typical (00h = not supported)
june 12, 2003 am29lv640mt/b 25 advance information table 10. device geometry definition addresses (x16) addresses (x8) data description 27h 4eh 0017h device size = 2 n byte 28h 29h 50h 52h 0002h 0000h flash device interface description (refer to cfi publication 100) 2ah 2bh 54h 56h 0005h 0000h max. number of byte in multi-byte write = 2 n (00h = not supported) 2ch 58h 0002h number of erase block regions within device (01h = uniform device, 02h = boot device) 2dh 2eh 2fh 30h 5ah 5ch 5eh 60h 007fh 0000h 0020h 0000h erase block region 1 information (refer to the cfi specification or cfi publication 100) 31h 32h 33h 34h 62h 64h 66h 68h 007eh 0000h 0000h 0001h erase block region 2 information (refer to cfi publication 100) 35h 36h 37h 38h 6ah 6ch 6eh 70h 0000h 0000h 0000h 0000h erase block region 3 information (refer to cfi publication 100) 39h 3ah 3bh 3ch 72h 74h 76h 78h 0000h 0000h 0000h 0000h erase block region 4 information (refer to cfi publication 100)
26 am29lv640mt/b june 12, 2003 advance information table 11. primary vendor-specific extended query command definitions writing specific address and data commands or se- quences into the command register initiates device op- erations. tables 12 and 13 define the valid register command sequences. writing incorrect address and data values or writing them in the improper sequence may place the device in an unknown state. a reset command is then required to return the device to read- ing array data. all addresses are latched on the falling edge of we# or ce#, whichever happens later. all data is latched on the rising edge of we# or ce#, whichever happens first. refer to the ac characteristics section for timing diagrams. reading array data the device is automatically set to reading array data after device power-up. no commands are required to retrieve data. the device is ready to read array data after completing an embedded program or embedded erase algorithm. after the device accepts an erase suspend command, the device enters the erase-suspend-read mode, after addresses (x16) addresses (x8) data description 40h 41h 42h 80h 82h 84h 0050h 0052h 0049h query-unique ascii string ?pri? 43h 86h 0031h major version number, ascii 44h 88h 0033h minor version number, ascii 45h 8ah 0008h address sensitive unlock (bits 1-0) 0 = required, 1 = not required process technology (bits 7-2) 0010b = 0.23 m mirrorbit 46h 8ch 0002h erase suspend 0 = not supported, 1 = to read only, 2 = to read & write 47h 8eh 0001h sector protect 0 = not supported, x = number of sectors in per group 48h 90h 0001h sector temporary unprotect 00 = not supported, 01 = supported 49h 92h 0004h sector protect/unprotect scheme 04 = 29lv800 mode 4ah 94h 0000h simultaneous operation 00 = not supported, x = number of sectors in bank 4bh 96h 0000h burst mode type 00 = not supported, 01 = supported 4ch 98h 0001h page mode type 00 = not supported, 01 = 4 word page, 02 = 8 word page 4dh 9ah 00b5h acc (acceleration) supply minimum 00h = not supported, d7-d4: volt, d3-d0: 100 mv 4eh 9ch 00c5h acc (acceleration) supply maximum 00h = not supported, d7-d4: volt, d3-d0: 100 mv 4fh 9eh 0002h/ 0003h top/bottom boot sector flag 00h = uniform device without wp# protect, 02h = bottom boot device, 03h = top boot device, 04h = uniform sectors bottom wp# protect, 05h = uniform sectors top wp# protect 50h a0h 0001h program suspend 00h = not supported, 01h = supported
june 12, 2003 am29lv640mt/b 27 advance information which the system can read data from any non-erase-suspended sector. after completing a pro- gramming operation in the erase suspend mode, the system may once again read array data with the same exception. see the erase suspend/erase resume commands section for more information. the system must issue the reset command to return the device to the read (or erase-suspend-read) mode if dq5 goes high during an active program or erase operation, or if the device is in the autoselect mode. see the next section, reset command , for more infor- mation. see also requirements for reading array data in the device bus operations section for more information. the read-only operations table provides the read pa- rameters, and figure 14 shows the timing diagram. reset command writing the reset command resets the device to the read or erase-suspend-read mode. address bits are don?t cares for this command. the reset command may be written between the se- quence cycles in an erase command sequence before erasing begins. this resets the device to the read mode. once erasure begins, however, the device ig- nores reset commands until the operation is complete. the reset command may be written between the sequence cycles in a program command sequence before programming begins. this resets the device to the read mode. if the program command sequence is written while the device is in the erase suspend mode, writing the reset command returns the device to the erase-suspend-read mode. once programming be- gins, however, the device ignores reset commands until the operation is complete. the reset command may be written between the se- quence cycles in an autoselect command sequence. once in the autoselect mode, the reset command must be written to return to the read mode. if the de- vice entered the autoselect mode while in the erase suspend mode, writing the reset command returns the device to the erase-suspend-read mode. if dq5 goes high during a program or erase operation, writing the reset command returns the device to the read mode (or erase-suspend-read mode if the device was in erase suspend). note that if dq1 goes high during a write buffer pro- gramming operation, the system must write the write-to-buffer-abort reset command sequence to reset the device for the next operation. autoselect command sequence the autoselect command sequence allows the host system to read several identifier codes at specific ad- dresses: note: the device id is read over three cycles. sa = sector address tables 12 and 13 show the address and data require- ments. this method is an alternative to that shown in ta b l e 4 , which is intended for prom programmers and requires v id on address pin a9. the autoselect command sequence may be written to an address that is either in the read or erase-suspend-read mode. the autoselect command may not be written while the de- vice is actively programming or erasing. the autoselect command sequence is initiated by first writing two unlock cycles. this is followed by a third write cycle that contains the autoselect command. the device then enters the autoselect mode. the system may read at any address any number of times without initiating another autoselect command sequence. the system must write the reset command to return to the read mode (or erase-suspend-read mode if the de- vice was previously in erase suspend). enter secsi sector/exit secsi sector command sequence the secsi sector region provides a secured data area containing an 8-word/16-byte random electronic serial number (esn). the system can access the secsi sector region by issuing the three-cycle enter secsi sector command sequence. the device continues to access the secsi sector region until the system is- sues the four-cycle exit secsi sector command se- quence. the exit secsi sector command sequence returns the device to normal operation. tables 12 and 13 show the address and data requirements for both command sequences. see also ?secsi (secured sili- con) sector flash memory region? for further informa- tion. word/byte program command sequence programming is a four-bus-cycle operation. the pro- gram command sequence is initiated by writing two unlock write cycles, followed by the program set-up command. the program address and data are written next, which in turn initiate the embedded program al- gorithm. the system is not required to provide further identifier code a7:a0 (x16) a6:a-1 (x8) manufacturer id 00h 00h device id, cycle 1 01h 02h device id, cycle 2 0eh 1ch device id, cycle 3 0fh 1eh secsi sector factory protect 03h 06h sector protect verify (sa)02h (sa)04h
28 am29lv640mt/b june 12, 2003 advance information controls or timings. the device automatically provides internally generated program pulses and verifies the programmed cell margin. tables 12 and 13 show the address and data requirements for the word program command sequence. note that the autoselect and cfi functions are unavailable when a program operation is in progress. when the embedded program algorithm is complete, the device then returns to the read mode and ad- dresses are no longer latched. the system can deter- mine the status of the program operation by using dq7 or dq6. refer to the write operation status sec- tion for information on these status bits. any commands written to the device during the em- bedded program algorithm are ignored. note that a hardware reset immediately terminates the program operation. the program command sequence should be reinitiated once the device has returned to the read mode, to ensure data integrity. programming is allowed in any sequence and across sector boundaries. a bit cannot be programmed from ?0? back to a ?1.? attempting to do so may cause the device to set dq5 = 1, or cause the dq7 and dq6 status bits to indicate the operation was suc- cessful. however, a succeeding read will show that the data is still ?0.? only er ase operations can convert a ?0? to a ?1.? unlock bypass command sequence the unlock bypass feature allows the system to pro- gram words to the device faster than using the stan- dard program command sequence. the unlock bypass command sequence is initiated by first writing two unlock cycles. this is followed by a third write cycle containing the unlock bypass command, 20h. the device then enters the unlock bypass mode. a two-cycle unlock bypass program command sequence is all that is required to program in this mode. the first cycle in this sequence contains the unlock bypass pro- gram command, a0h; the second cycle contains the program address and data. additional data is pro- grammed in the same manner. this mode dispenses with the initial two unlock cycles required in the stan- dard program command sequence, resulting in faster total programming time. tables 12 and 13 show the re- quirements for the command sequence. during the unlock bypass mode, only the unlock by- pass program and unlock bypass reset commands are valid. to exit the unlock bypass mode, the system must issue the two-cycle unlock bypass reset com- mand sequence. the first cycle must contain the data 90h. the second cycle must contain the data 00h. the device then returns to the read mode. write buffer programming write buffer programming allows the system write to a maximum of 16 words/32 bytes in one programming operation. this results in faster effective programming time than the standard programming algorithms. the write buffer programming command sequence is initi- ated by first writing two unlock cycles. this is followed by a third write cycle containing the write buffer load command written at the sector address in which pro- gramming will occur. the fourth cycle writes the sector address and the number of word locations, minus one, to be programmed. for example, if the system will pro- gram 6 unique address locations, then 05h should be written to the device. this tells the device how many write buffer addresses will be loaded with data and therefore when to expect the program buffer to flash command. the number of locations to program cannot exceed the size of the write buffer or the operation will abort. the fifth cycle writes the first address location and data to be programmed. the write-buffer-page is se- lected by address bits a max ?a 4 . all subsequent ad- dress/data pairs must fall within the selected-write-buffer-page. the system then writes the remaining address/data pairs into the write buffer. write buffer locations may be loaded in any order. the write-buffer-page address must be the same for all address/data pairs loaded into the write buffer. (this means write buffer programming cannot be per- formed across multiple write-buffer pages. this also means that write buffer programming cannot be per- formed across multiple sectors. if the system attempts to load programming data outside of the selected write-buffer page, the operation will abort. note that if a write buffer address location is loaded multiple times, the address/data pair counter will be decremented for every data load operation. the host system must therefore account for loading a write-buffer location more than once. the counter decrements for each data load operation, not for each unique write-buffer-address location. note also that if an address location is loaded more than once into the buffer, the final data loaded for that address will be programmed. once the specified number of write buffer locations have been loaded, the system must then write the pro- gram buffer to flash command at the sector address. any other address and data combination aborts the write buffer programming operation. the device then begins programming. data polling should be used while monitoring the last address location loaded into the write buffer. dq7, dq6, dq5, and dq1 should be monitored to determine the device status during write buffer programming.
june 12, 2003 am29lv640mt/b 29 advance information the write-buffer programming operation can be sus- pended using the standard program suspend/resume commands. upon successful completion of the write buffer programming operation, the device is ready to execute the next command. the write buffer programming sequence can be aborted in the following ways: load a value that is greater than the page buffer size during the number of locations to program step. write to an address in a sector different than the one specified during the write-buffer-load com- mand. write an address/data pair to a different write-buffer-page than the one selected by the starting address during the write buffer data load- ing stage of the operation. write data other than the confirm command after the specified number of data load cycles. the abort condition is indicated by dq1 = 1, dq7 = data# (for the last address location loaded), dq6 = toggle, and dq5=0. a write-to-buffer-abort reset command sequence must be written to reset the de- vice for the next operation. note that the full 3-cycle write-to-buffer-abort reset command sequence is re- quired when using write-buffer-programming features in unlock bypass mode. accelerated program the device offers accelerated program operations through the wp#/acc pin. when the system asserts v hh on the wp#/acc pin, the device automatically en- ters the unlock bypass mode. the system may then write the two-cycle unlock bypass program command sequence. the device uses the higher voltage on the wp#/acc pin to accelerate the operation. note that the wp#/ acc pin must not be at v hh for operations other than accelerated programming, or device dam- age may result. in addition, no external pullup is nec- essary since the wp#/acc pin has internal pullup to v cc . figure 5 illustrates the algorithm for the program oper- ation. refer to the erase and program operations table in the ac characteristics section for parameters, and figure 17 for timing diagrams.
30 am29lv640mt/b june 12, 2003 advance information figure 4. write buffer programming operation write ?write to buffer? command and sector address write number of addresses to program minus 1(wc) and sector address write program buffer to flash sector address write first address/data write to a different sector address fail or abort pass read dq7 - dq0 at last loaded address read dq7 - dq0 with address = last loaded address write next address/data pair wc = wc - 1 wc = 0 ? part of ?write to buffer? command sequence ye s ye s ye s ye s ye s ye s no no no no no no abort write to buffer operation? dq7 = data? dq7 = data? dq5 = 1? dq1 = 1? write to buffer aborted. must write ?write-to-buffer abort reset? command sequence to return to read mode. notes: 1. when sector address is specified, any address in the selected sector is acceptable. however, when loading write-buffer address locations with data, all addresses must fall within the selected write-buffer page. 2. dq7 may change simultaneously with dq5. therefore, dq7 should be verified. 3. if this flowchart location was reached because dq5= ?1?, then the device failed. if this flowchart location was reached because dq1= ?1?, then the write to buffer operation was aborted. in either case, the proper reset command must be written before the device can begin another operation. if dq1=1, write the write-buffer-programming-abort-reset command. if dq5=1, write the reset command. 4. see table 13 for command sequences required for write buffer programming. (note 3) (note 1) (note 2)
june 12, 2003 am29lv640mt/b 31 advance information figure 5. program operation program suspend/program resume command sequence the program suspend command allows the system to interrupt a programming operation or a write to buffer programming operation so that data can be read from any non-suspended sector. when the program sus- pend command is written during a programming pro- cess, the device halts the program operation within 15 s maximum (5 s typical) and updates the status bits. addresses are not required when writing the program suspend command. after the programming operation has been sus- pended, the system can read array data from any non-suspended sector. the program suspend com- mand may also be issued during a programming oper- ation while an erase is suspended. in this case, data may be read from any addresses not in erase sus- pend or program suspend. if a read is needed from the secsi sector area (one-time program area), then user must use the proper command sequences to enter and exit this region. the system may also write the autoselect command sequence when the device is in the program suspend mode. the system can read as many autoselect codes as required. when the device exits the autose- lect mode, the device reverts to the program suspend mode, and is ready for another valid operation. see autoselect command sequence for more information. after the program resume command is written, the device reverts to programming. the system can de- termine the status of the program operation using the dq7 or dq6 status bits, just as in the standard pro- gram operation. see write operation status for more information. the system must write the program resume com- mand (address bits are don?t care) to exit the program suspend mode and continue the programming opera- tion. further writes of the resume command are ig- nored. another program suspend command can be written after the device has resume programming. start write program command sequence data poll from system verify data? no yes last address? no yes programming completed increment address embedded program algorithm in progress note: see table 13 for program command sequence.
32 am29lv640mt/b june 12, 2003 advance information figure 6. program suspend/program resume chip erase command sequence chip erase is a six bus cycle operation. the chip erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two additional unlock write cycles are then followed by the chip erase command, which in turn invokes the embedded erase algorithm. the device does not require the system to preprogram prior to erase. the embedded erase algo- rithm automatically preprograms and verifies the entire memory for an all zero data pattern prior to electrical erase. the system is not required to provide any con- trols or timings during these operations. tables 12 and 13 shows the address and data requirements for the chip erase command sequence. note that the autose- lect and cfi functions are unavailable when an erase operation is in progress. when the embedded erase algorithm is complete, the device returns to the read mode and addresses are no longer latched. the system can determine the status of the erase operation by using dq7, dq6, or dq2. refer to the write operation status section for infor- mation on these status bits. any commands written during the chip erase operation are ignored. however, note that a hardware reset im- mediately terminates the erase operation. if that oc- curs, the chip erase command sequence should be reinitiated once the device has returned to reading array data, to ensure data integrity. figure 7 illustrates the algorithm for the erase opera- tion. refer to the erase and program operations ta- bles in the ac characteristics section for parameters, and figure 19 section for timing diagrams. sector erase command sequence sector erase is a six bus cycle operation. the sector erase command sequence is initiated by writing two unlock cycles, followed by a set-up command. two ad- ditional unlock cycles are written, and are then fol- lowed by the address of the sector to be erased, and the sector erase command. tables 12 and 13 shows the address and data requirements for the sector erase command sequence. note that the autoselect and cfi functions are unavailable when an erase op- eration is in progress. the device does not require the system to preprogram prior to erase. the embedded erase algorithm auto- matically programs and verifies the entire memory for an all zero data pattern prior to electrical erase. the system is not required to provide any controls or tim- ings during these operations. after the command sequence is written, a sector erase time-out of 50 s occurs. during the time-out period, additional sector addresses and sector erase com- mands may be written. loading the sector erase buffer may be done in any sequence, and the number of sec- tors may be from one sector to all sectors. the time between these additional cycles must be less than 50 s, otherwise erasure may begin. any sector erase address and command following the exceeded time-out may or may not be accepted. it is recom- mended that processor interrupts be disabled during this time to ensure all commands are accepted. the interrupts can be re-enabled after the last sector erase command is written. any command other than sector erase or erase suspend during the time-out period resets the device to the read mode. the system must rewrite the command se- quence and any additional addresses and commands. the system can monitor dq3 to determine if the sec- tor erase timer has timed out (see the section on dq3: sector erase timer.). the time-out begins from the ris- program operation or write-to-buffer sequence in progress write program suspend command sequence command is also valid for erase-suspended-program operations autoselect and secsi sector read operations are also allowed data cannot be read from erase- o r program-suspended sectors write program resume command sequence read data as required done reading? no yes write address/data xxxh/30h device reverts to operation prior to program suspend write address/data xxxh/b0h wait 15 s
june 12, 2003 am29lv640mt/b 33 advance information ing edge of the final we# pulse in the command sequence. when the embedded erase algorithm is complete, the device returns to reading array data and addresses are no longer latched. the system can determine the status of the erase operation by reading dq7, dq6, or dq2 in the erasing sector. refer to the write opera- tion status section for information on these status bits. once the sector erase operation has begun, only the erase suspend command is valid. all other com- mands are ignored. however, note that a hardware reset immediately terminates the erase operation. if that occurs, the sector erase command sequence should be reinitiated once the device has returned to reading array data, to ensure data integrity. figure 7 illustrates the algor ithm for the erase opera- tion. refer to the erase and program operations ta- bles in the ac characteristics section for parameters, and figure 19 section for timing diagrams. figure 7. erase operation erase suspend/erase resume commands the erase suspend command, b0h, allows the sys- tem to interrupt a sector erase operation and then read data from, or program data to, any sector not selected for erasure. this command is valid only during the sector erase operation, including the 50 s time-out period during the sector erase command sequence. the erase suspend command is ignored if written dur- ing the chip erase operation or embedded program algorithm. when the erase suspend command is written during the sector erase operation, the device requires a typi- cal of 5 s (maximum of 20 s) to suspend the erase operation. however, when the erase suspend com- mand is written during the sector erase time-out, the device immediately terminates the time-out period and suspends the erase operation. after the erase operation has been suspended, the device enters the erase-suspend-read mode. the sys- tem can read data from or program data to any sector not selected for erasure. (the device ?erase sus- pends? all sectors selected for erasure.) reading at any address within erase-suspended sectors pro- duces status information on dq7?dq0. the system can use dq7, or dq6 and dq2 together, to determine if a sector is actively erasing or is erase-suspended. refer to the write operation status section for infor- mation on these status bits. after an erase-suspended program operation is com- plete, the device returns to the erase-suspend-read mode. the system can determine the status of the program operation using the dq7 or dq6 status bits, just as in the standard word program operation. refer to the write operation status section for more information. in the erase-suspend-read mode, the system can also issue the autoselect command sequence. refer to the autoselect mode and autoselect command sequence sections for details. to resume the sector erase operation, the system must write the erase resume command. the address of the erase-suspended sector is required when writ- ing this command. further writes of the resume com- mand are ignored. another erase suspend command can be written after the chip has resumed erasing. start write erase command sequence (notes 1, 2) data poll to erasing bank from system data = ffh? no yes erasure completed embedded erase algorithm in progress notes: 1. see table 12 and table 13 for erase command sequence. 2. see the section on dq3 for information on the sector erase timer.
34 am29lv640mt/b june 12, 2003 advance information command definitions table 12. command definitions (x16 mode, byte# = v ih ) legend: x = don?t care ra = read address of the memory location to be read. rd = read data read from location ra during read operation. pa = program address . addresses latch on the falling edge of the we# or ce# pulse, whichever happens later. pd = program data for location pa. data latches on the rising edge of we# or ce# pulse, whichever happens first. sa = sector address of sector to be verified (in autoselect mode) or erased. address bits a21?a15 uniquely select any sector. wbl = write buffer location. address must be within the same write buffer page as pa. wc = word count. number of write buffer locations to load minus 1. notes: 1. see table 1 for description of bus operations. 2. all values are in hexadecimal. 3. except for the read cycle and the fourth cycle of the autoselect command sequence, all bus cycles are write cycles. 4. during unlock cycles, when lower address bits are 555 or 2aah as shown in table, address bits higher than a11 (except where ba is required) and data bits higher than dq7 are don?t cares. 5. no unlock or command cycles required when device is in read mode. 6. the reset command is required to return to the read mode (or to the erase-suspend-read mode if previously in erase suspend) when the device is in the autoselect mode, or if dq5 goes high while the device is providing status information. 7. the fourth cycle of the autoselect command sequence is a read cycle. data bits dq15?dq8 are don?t care. except rd, pd and wc. see the autoselect command sequence section for more information. 8. the device id must be read in three cycles. the data is 2201h for top boot and 2200h for bottom boot. 9. if wp# protects the top two address sectors, the data is 98h for factory locked and 18h for not factory locked. if wp# protects the bottom two address sectors, the data is 88h for factory locked and 08h for not factor locked. 10. the data is 00h for an unprotected sector group and 01h for a protected sector group. 11. the total number of cycles in the command sequence is determined by the number of words written to the write buffer. the maximum number of cycles in the command sequence is 21. 12. command sequence resets device for next command after aborted write-to-buffer operation. 13. the unlock bypass command is required prior to the unlock bypass program command. 14. the unlock bypass reset command is required to return to the read mode when the device is in the unlock bypass mode. 15. the system may read and program in non-erasing sectors, or enter the autoselect mode, when in the erase suspend mode. the erase suspend command is valid only during a sector erase operation. 16. the erase resume command is valid only during the erase suspend mode. 17. command is valid when device is ready to read array data or when device is in autoselect mode. command sequence (notes) cycles bus cycles (notes 1?4) first second third fourth fifth sixth addr data addr data addr data addr data addr data addr data read (note 5) 1 ra rd reset (note 6) 1 xxx f0 autoselect (note 7) manufacturer id 4 555 aa 2aa 55 555 90 x00 0001 device id (note 8) 6 555 aa 2aa 55 555 90 x01 227e x0e 2210 x0f 2200/ 2201 secsi ? sector factory protect (note 9) 4 555 aa 2aa 55 555 90 x03 (note 9) sector group protect verify (note 10) 4 555 aa 2aa 55 555 90 (sa)x02 00/01 enter secsi sector region 3 555 aa 2aa 55 555 88 exit secsi sector region 4 555 aa 2aa 55 555 90 xxx 00 program 4 555 aa 2aa 55 555 a0 pa pd write to buffer (note 11) 6 555 aa 2aa 55 sa 25 sa wc pa pd wbl pd program buffer to flash 1 sa 29 write to buffer abort reset (note 12) 3 555 aa 2aa 55 555 f0 unlock bypass 3 555 aa 2aa 55 555 20 unlock bypass program (note 13) 2 xxx a0 pa pd unlock bypass reset (note 14) 2 xxx 90 xxx 00 chip erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 555 10 sector erase 6 555 aa 2aa 55 555 80 555 aa 2aa 55 sa 30 program/erase suspend (note 15) 1 ba b0 program/erase resume (note 16) 1 ba 30 cfi query (note 17) 1 55 98
june 12, 2003 am29lv640mt/b 35 advance information table 13. command definitions (x8 mode, byte# = v il ) legend: x = don?t care ra = read address of the memory location to be read. rd = read data read from location ra during read operation. pa = program address . addresses latch on the falling edge of the we# or ce# pulse, whichever happens later. pd = program data for location pa. data latches on the rising edge of we# or ce# pulse, whichever happens first. sa = sector address of sector to be verified (in autoselect mode) or erased. address bits a21?a15 uniquely select any sector. wbl = write buffer location. address must be within the same write buffer page as pa. bc = byte count. number of write buffer locations to load minus 1. notes: 1. see table 1 for description of bus operations. 2. all values are in hexadecimal. 3. except for the read cycle and the fourth cycle of the autoselect command sequence, all bus cycles are write cycles. 4. during unlock cycles, when lower address bits are 555 or aaah as shown in table, address bits higher than a11 (except where ba is required) and data bits higher than dq7 are don?t cares. 5. no unlock or command cycles required when device is in read mode. 6. the reset command is required to return to the read mode (or to the erase-suspend-read mode if previously in erase suspend) when the device is in the autoselect mode, or if dq5 goes high while the device is providing status information. 7. the fourth cycle of the autoselect command sequence is a read cycle. data bits dq15?dq8 are don?t care. see the autoselect command sequence section for more information. 8. the device id must be read in three cycles. the data is 01h for top boot and 00h for bottom boot 9. if wp# protects the top two address sectors, the data is 98h for factory locked and 18h for not factory locked. if wp# protects the bottom two address sectors, the data is 88h for factory locked and 08h for not factor locked. 10. the data is 00h for an unprotected sector group and 01h for a protected sector group. 11. the total number of cycles in the command sequence is determined by the number of words written to the write buffer. the maximum number of cycles in the command sequence is 37. 12. command sequence resets device for next command after aborted write-to-buffer operation. 13. the unlock bypass command is required prior to the unlock bypass program command. 14. the unlock bypass reset command is required to return to the read mode when the device is in the unlock bypass mode. 15. the system may read and program in non-erasing sectors, or enter the autoselect mode, when in the erase suspend mode. the erase suspend command is valid only during a sector erase operation. 16. the erase resume command is valid only during the erase suspend mode. 17. command is valid when device is ready to read array data or when device is in autoselect mode. command sequence (notes) cycles bus cycles (notes 1?4) first second third fourth fifth sixth addr data addr data addr data addr data addr data addr data read (note 5) 1 ra rd reset (note 6) 1 xxx f0 autoselect (note 7) manufacturer id 4 aaa aa 555 55 aaa 90 x00 01 device id (note 8) 6 aaa aa 555 55 aaa 90 x02 7e x1c 10 x1e 00/01 secsi ? sector factory protect (note 9) 4 aaa aa 555 55 aaa 90 x06 (note 9) sector group protect verify (note 10) 4 aaa aa 555 55 aaa 90 (sa)x04 00/01 enter secsi sector region 3 aaa aa 555 55 aaa 88 exit secsi sector region 4 aaa aa 555 55 aaa 90 xxx 00 program 4 aaa aa 555 55 aaa a0 pa pd write to buffer (note 11) 6 aaa aa 555 55 sa 25 sa bc pa pd wbl pd program buffer to flash 1 sa 29 write to buffer abort reset (note 12) 3 aaa aa 555 55 aaa f0 unlock bypass 3 aaa aa 555 55 aaa 20 unlock bypass program (note 13) 2 xxx a0 pa pd unlock bypass reset (note 14) 2 xxx 90 xxx 00 chip erase 6 aaa aa 555 55 aaa 80 aaa aa 555 55 aaa 10 sector erase 6 aaa aa 555 55 aaa 80 aaa aa 555 55 sa 30 program/erase suspend (note 15) 1 ba b0 program/erase resume (note 16) 1 ba 30 cfi query (note 17) 1 aa 98
36 am29lv640mt/b june 12, 2003 advance information write operation status the device provides several bits to determine the status of a program or erase operation: dq2, dq3, dq5, dq6, and dq7. table 14 and the following subsections describe the function of these bits. dq7 and dq6 each offer a method for determining whether a program or erase operation is complete or in progress. the device also provides a hardware-based output signal, ry/by#, to determine whether an embedded program or erase operation is in progress or has been completed. dq7: data# polling the data# polling bit, dq7, indicates to the host system whether an embedded program or erase algorithm is in progress or completed, or whether the device is in erase suspend. data# polling is valid after the rising edge of the final we# pulse in the command sequence. during the embedded program algorithm, the device out- puts on dq7 the complement of the datum programmed to dq7. this dq7 status also applies to programming during erase suspend. when the embedded program algorithm is complete, the device outputs the datum programmed to dq7. the system must provide the program address to read valid status information on dq7. if a program address falls within a protected sector, data# polling on dq7 is ac- tive for approximately 1 s, then the device returns to the read mode. during the embedded erase algorithm, data# polling produces a ?0? on dq7. when the embedded erase algorithm is complete, or if the device enters the erase suspend mode, data# polling produces a ?1? on dq7. the system must provide an address within any of the sectors selected for erasure to read valid status infor- mation on dq7. after an erase command sequence is written, if all sectors selected for erasing are protected, data# poll- ing on dq7 is active for approximately 100 s, then the device returns to the read mode. if not all selected sectors are protected, the embedded erase algorithm erases the unprotected sectors, and ignores the se- lected sectors that are protected. however, if the sys- tem reads dq7 at an address within a protected sector, the status may not be valid. just prior to the completion of an embedded program or erase operation, dq7 may change asynchronously with dq0?dq6 while output enable (oe#) is asserted low. that is, the device may change from providing status information to valid data on dq7. depending on when the system samples the dq7 output, it may read the status or valid data. even if the device has com- pleted the program or erase operation and dq7 has valid data, the data outputs on dq0?dq6 may be still invalid. valid data on dq0?dq7 will appear on suc- cessive read cycles. table 14 shows the outputs for data# polling on dq7. figure 8 shows the data# polling algorithm. figure 20 in the ac characteristics section shows the data# polling timing diagram. figure 8. data# polling algorithm dq7 = data? yes no no dq5 = 1? no yes yes fail pass read dq7?dq0 addr = va read dq7?dq0 addr = va dq7 = data? start notes: 1. va = valid address for programming. during a sector erase operation, a valid address is any sector address within the sector being erased. during chip erase, a valid address is any non-protected sector address. 2. dq7 should be rechecked even if dq5 = ?1? because dq7 may change simultaneously with dq5.
june 12, 2003 am29lv640mt/b 37 advance information ry/by#: ready/busy# the ry/by# is a dedicated, open-drain output pin which indicates whether an embedded algorithm is in progress or complete. the ry/by# status is valid after the rising edge of the final we# pulse in the command sequence. since ry/by# is an open-drain output, sev- eral ry/by# pins can be tied together in parallel with a pull-up resistor to v cc . if the output is low (busy), the device is actively eras- ing or programming. (this includes programming in the erase suspend mode.) if the output is high (ready), the device is in the read mode, the standby mode, or in the erase-suspend-read mode. table 14 shows the outputs for ry/by#. dq6: toggle bit i toggle bit i on dq6 indicates whether an embedded program or erase algorithm is in progress or com- plete, or whether the device has entered the erase suspend mode. toggle bit i may be read at any ad- dress, and is valid after the rising edge of the final we# pulse in the command sequence (prior to the program or erase operation), and during the sector erase time-out. during an embedded program or erase algorithm op- eration, successive read cycles to any address cause dq6 to toggle. the system may use either oe# or ce# to control the read cycles. when the operation is complete, dq6 stops toggling. after an erase command sequence is written, if all sectors selected for erasing are protec ted, dq6 toggles for approxi- mately 100 s, then returns to reading array data. if not all selected sectors are protected, the embedded erase algo- rithm erases the unprotected sectors, and ignores the se- lected sectors that are protected. the system can use dq6 and dq2 together to determine whether a sector is actively erasing or is erase-suspended. when the device is actively erasing (that is, the embedded erase algorithm is in progress), dq6 toggles. when the de- vice enters the erase suspend mode, dq6 stops toggling. however, the system must also use dq2 to determine which sectors are erasing or erase-suspended. alterna- tively, the system can use dq7 (see the subsection on dq7: data# polling ). if a program address falls within a protected sector, dq6 toggles for approximately 1 s after the program command sequence is written, then returns to reading array data. dq6 also toggles during the erase-suspend-program mode, and stops toggling once the embedded pro- gram algorithm is complete. table 14 shows the outputs for toggle bit i on dq6. figure 9 shows the toggle bit algorithm. figure 21 in the ?ac characteristics? section shows the toggle bit timing diagrams. figure 22 shows the differences be- tween dq2 and dq6 in graphical form. see also the subsection on dq2: toggle bit ii .
38 am29lv640mt/b june 12, 2003 advance information figure 9. toggle bit algorithm dq2: toggle bit ii the ?toggle bit ii? on dq2, when used with dq6, indi- cates whether a particular sector is actively erasing (that is, the embedded erase algorithm is in progress), or whether that sector is erase-suspended. toggle bit ii is valid after the rising edge of the final we# pulse in the command sequence. dq2 toggles when the system reads at addresses within those sectors that have been selected for era- sure. (the system may use either oe# or ce# to con- trol the read cycles.) but dq2 cannot distinguish whether the sector is actively erasing or is erase-sus- pended. dq6, by comparison, indicates whether the device is actively erasing, or is in erase suspend, but cannot distinguish which sectors are selected for era- sure. thus, both status bits are required for sector and mode information. refer to table 14 to compare out- puts for dq2 and dq6. figure 9 shows the toggle bit algorithm in flowchart form, and the section ?dq2: toggle bit ii? explains the algorithm. see also the ry/by#: ready/busy# sub- section. figure 21 shows the toggle bit timing diagram. figure 22 shows the differences between dq2 and dq6 in graphical form. reading toggle bits dq6/dq2 refer to figure 9 for the following discussion. when- ever the system initially be gins reading toggle bit sta- tus, it must read dq7?dq0 at least twice in a row to determine whether a toggle bit is toggling. typically, the system would note and store the value of the tog- gle bit after the first read. after the second read, the system would compare the new value of the toggle bit with the first. if the toggle bit is not toggling, the device has completed the program or erase operation. the system can read array data on dq7?dq0 on the fol- lowing read cycle. however, if after the initial two read cycles, the system determines that the toggle bit is still toggling, the sys- tem also should note whether the value of dq5 is high (see the section on dq5). if it is, the system should then determine again whether the toggle bit is tog- gling, since the toggle bit may have stopped toggling just as dq5 went high. if the toggle bit is no longer toggling, the device has successfully completed the program or erase operation. if it is still toggling, the de- vice did not completed the operation successfully, and the system must write the reset command to return to reading array data. the remaining scenario is that the system initially de- termines that the toggle bit is toggling and dq5 has not gone high. the system may continue to monitor the toggle bit and dq5 through successive read cy- cles, determining the status as described in the previ- ous paragraph. alternatively, it may choose to perform start no yes yes dq5 = 1? no yes toggle bit = toggle? no program/erase operation not complete, write reset command program/erase operation complete read dq7?dq0 toggle bit = toggle? read dq7?dq0 twice read dq7?dq0 note: the system should recheck the toggle bit even if dq5 = ?1? because the toggle bit may stop toggling as dq5 changes to ?1.? see the subsections on dq6 and dq2 for more information.
june 12, 2003 am29lv640mt/b 39 advance information other system tasks. in this case, the system must start at the beginning of the algorithm when it returns to de- termine the status of the operation (top of figure 9). dq5: exceeded timing limits dq5 indicates whether the program, erase, or write-to-buffer time has exceeded a specified internal pulse count limit. under these conditions dq5 produces a ?1,? indicating that the program or erase cycle was not suc- cessfully completed. the device may output a ?1? on dq5 if the system tries to program a ?1? to a location that was previously pro- grammed to ?0.? only an erase operation can change a ?0? back to a ?1.? under this condition, the device halts the operation, and when the timing limit has been exceeded, dq5 produces a ?1.? in all these cases, the system must write the reset command to return the device to the reading the array (or to erase-suspend-read if the device was previously in the erase-suspend-program mode). dq3: sector erase timer after writing a sector erase command sequence, the system may read dq3 to determine whether or not erasure has begun. (the sector erase timer does not apply to the chip erase command.) if additional sectors are selected for erasure, the entire time-out also applies after each additional sector erase com- mand. when the time-out period is complete, dq3 switches from a ?0? to a ?1.? if the time between addi- tional sector erase commands from the system can be assumed to be less than 50 s, the system need not monitor dq3. see also the sector erase command sequence section. after the sector erase command is written, the system should read the status of dq7 (data# polling) or dq6 (toggle bit i) to ensure that the device has accepted the command sequence, and then read dq3. if dq3 is ?1,? the embedded erase algorithm has begun; all fur- ther commands (except erase suspend) are ignored until the erase operation is complete. if dq3 is ?0,? the device will accept additional sector erase commands. to ensure the command has been accepted, the sys- tem software should check the status of dq3 prior to and following each subsequent sector erase com- mand. if dq3 is high on the second status check, the last command might not have been accepted. table 14 shows the status of dq3 relative to the other status bits. dq1: write-to-buffer abort dq1 indicates whether a write-to-buffer operation was aborted. under these conditions dq1 produces a ?1?. the system must issue the write-to-buffer-abort-reset command sequence to re- turn the device to reading array data. see write buffer table 14. write operation status notes: 1. dq5 switches to ?1? when an embedded program, embedded er ase, or write-to-buffer operation has exceeded the maximum timing limits. refer to the section on dq5 for more information. 2. dq7 and dq2 require a valid address when reading status information. refer to the appropriate subsection for further details. 3. the data# polling algorithm should be used to monitor the last loaded write-buffer address location. 4. dq1 switches to ?1? when tthe device has aborted the write-to-buffer operation. status dq7 (note 2) dq6 dq5 (note 1) dq3 dq2 (note 2) dq1 ry/by# standard mode embedded program algorithm dq7# toggle 0 n/a no toggle 0 0 embedded erase algorithm 0 toggle 0 1 toggle n/a 0 program suspend mode program- suspend read program-suspended sector invalid (not allowed) 1 non-program suspended sector data 1 erase suspend mode erase- suspend read erase-suspended sector 1 no toggle 0 n/a toggle n/a 1 non-erase suspended sector data 1 erase-suspend-program (embedded program) dq7# toggle 0 n/a n/a n/a 0 write-to- buffer busy (note 3) dq7# toggle 0 n/a n/a 0 0 abort (note 4) dq7# toggle 0 n/a n/a 1 0
40 am29lv640mt/b june 12, 2003 advance information absolute maximum ratings storage temperature plastic packages . . . . . . . . . . . . . . . ?65 c to +150 c ambient temperature with power applied . . . . . . . . . . . . . ?65 c to +125 c voltage with respect to ground v cc (note 1) . . . . . . . . . . . . . . . . .?0.5 v to +4.0 v v io . . . . . . . . . . . . . . . . . . . . . . . . .?0.5 v to +4.0 v a9 , oe#, acc, and reset# (note 2) . . . . . . . . . . . . . . . . . . . .?0.5 v to +12.5 v all other pins (note 1) . . . . . . ?0.5 v to v cc +0.5 v output short circuit current (note 3) . . . . . . 200 ma notes: 1. minimum dc voltage on input or i/o pins is ?0.5 v. during voltage transitions, input or i/o pins may overshoot v ss to ?2.0 v for periods of up to 20 ns. maximum dc voltage on input or i/o pins is v cc +0.5 v. see figure 10. during voltage transitions, input or i/o pins may overshoot to v cc +2.0 v for periods up to 20 ns. see figure 11. 2. minimum dc input voltage on pins a9, oe#, acc, and reset# is ?0.5 v. during voltage transitions, a9, oe#, acc, and reset# may overshoot v ss to ?2.0 v for periods of up to 20 ns. see figure 10. maximum dc input voltage on pin a9, oe#, acc, and reset# is +12.5 v which may overshoot to +14.0 v for periods up to 20 ns. 3. no more than one output may be shorted to ground at a time. duration of the short circuit should not be greater than one second. stresses above those listed under ?absolute maximum ratings? may cause permanent damage to the device. this is a stress rating only; functional operation of the device at these or any other conditions above those indicated in the operational sections of this data sheet is not implied. exposure of the device to absolute maximum rating conditions for extended periods may affect device reliability. operating ranges industrial (i) devices ambient temperature (t a ) . . . . . . . . . ?40c to +85c supply voltages v cc for full voltage range . . . . . . . . . . . . . . . 2.7?3.6 v v cc for regulated voltage range . . . . . . . . . . 3.0?3.6 v note: operating ranges define those limits between which the functionality of the device is guaranteed. 20 ns 20 ns +0.8 v ?0.5 v 20 ns ?2.0 v figure 10. maximum negative overshoot waveform 20 ns 20 ns v cc +2.0 v v cc +0.5 v 20 ns 2.0 v figure 11. maximum positive overshoot waveform
june 12, 2003 am29lv640mt/b 41 advance information dc characteristics cmos compatible notes: 1. on the wp#/acc pin only, the maximum input load current when wp# = v il is 5.0 a. 2. the i cc current listed is typically less than 2 ma/mhz, with oe# at v ih . 3. maximum i cc specifications are tested with v cc = v cc max. 4. i cc active while embedded erase or embedded program is in progress. 5. automatic sleep mode enables the low power mode when addresses remain stable for t acc + 30 ns. 6. not 100% tested. 7. includes ry/by# parameter symbol parameter description (notes) test conditions min typ max unit i li input load current (1) v in = v ss to v cc , v cc = v cc max 1.0 a i lit a9, acc input load current v cc = v cc max ; a9 = 12.5 v 35 a i lo output leakage current v out = v ss to v cc , v cc = v cc max 1.0 a i lr reset leakage current v cc = v cc max ; reset= 12.5 v 35 a i cc1 v cc active read current (2, 3) ce# = v il, oe# = v ih , 5 mhz 15 20 ma 1 mhz 15 20 i cc2 v cc initial page read current (2, 3) ce# = v il, oe# = v ih 30 50 ma i cc3 v cc intra-page read current (2, 3) ce# = v il, oe# = v ih 10 20 ma i cc4 v cc active write current (3, 4) ce# = v il, oe# = v ih 50 60 ma i cc5 v cc standby current (3) ce#, reset# = v cc 0.3 v, wp# = v ih 15a i cc6 v cc reset current (3) reset# = v ss 0.3 v, wp# = v ih 15a i cc7 automatic sleep mode (3, 5) v ih = v cc 0.3 v; v il = v ss 0.3 v, wp# = v ih 15a v il input low voltage ?0.5 0.8 v v ih input high voltage 1.9 v cc + 0.5 v v id voltage for autoselect and temporary sector unprotect v cc = 2.7 ?3.6 v 11.5 12.5 v v ol output low voltage i ol = 4.0 ma, v cc = v cc min 0.15 x v cc v v oh1 output high voltage i oh = ?2.0 ma, v cc = v cc min 0.85 v cc v v oh2 i oh = ?100 a, v cc = v cc min v cc ?0.4 v v lko low v cc lock-out voltage (6) 2.3 2.5 v
42 am29lv640mt/b june 12, 2003 advance information test conditions table 15. test specifications note: if v io < v cc , the reference level is 0.5 v io . key to switching waveforms 2.7 k ? c l 6.2 k ? 3.3 v device under te s t note: diodes are in3064 or equivalent figure 12. test setup test condition all speeds unit output load 1 ttl gate output load capacitance, c l (including jig capacitance) 30 pf input rise and fall times 5 ns input pulse levels 0.0?3.0 v input timing measurement reference levels (see note) 1.5 v output timing measurement reference levels 0.5 v io v waveform inputs outputs steady changing from h to l changing from l to h don?t care, any change permitted changing, state unknown does not apply center line is high impedance state (high z) 3.0 v 0.0 v 1.5 v 0.5 v io v output measurement level input note: if v io < v cc , the input measurement reference level is 0.5 v io . figure 13. input waveforms and measurement levels
june 12, 2003 am29lv640mt/b 43 advance information ac characteristics read-only operations notes: 1. not 100% tested. 2. see figure 12 and table 15 for test specifications. parameter description test setup speed options jedec std. 90r 100r 100 110r 110, 120r 120 unit t avav t rc read cycle time (note 1) min 90 100 110 120 ns t avqv t acc address to output delay ce#, oe# = v il max 90 100 110 120 ns t elqv t ce chip enable to output delay oe# = v il max 90 100 110 120 ns t pac c page access time max 25 30 30 40 30 40 ns t glqv t oe output enable to output delay max 25 30 30 40 30 40 ns t ehqz t df chip enable to output high z (note 1) max 16 ns t ghqz t df output enable to output high z (note 1) max 16 ns t axqx t oh output hold time from addresses, ce# or oe#, whichever occurs first min 0 ns t oeh output enable hold time (note 1) read min 0 ns toggle and data# polling min 10 ns t oh t ce outputs we# addresses ce# oe# high z output valid high z addresses stable t rc t acc t oeh t rh t oe t rh 0 v ry/by# reset# t df figure 14. read operation timings
44 am29lv640mt/b june 12, 2003 advance information ac characteristics * figure shows word mode. addresses are a1?a-1 for byte mode. figure 15. page read timings a21 - a2 ce# oe# a1 - a0 data bus same page aa ab ac ad qa qb qc qd t acc t pac c t pac c t pac c
june 12, 2003 am29lv640mt/b 45 advance information ac characteristics hardware reset (reset#) note: not 100% tested. parameter description all speed options unit jedec std. t ready reset# pin low (during embedded algorithms) to read mode (see note) max 20 s t ready reset# pin low (not during embedded algorithms) to read mode (see note) max 500 ns t rp reset# pulse width min 500 ns t rh reset high time before read (see note) min 50 ns t rpd reset# low to standby mode min 20 s reset# ry/by# ry/by# t rp t ready reset timings not during embedded algorithms t ready ce#, oe# t rh ce#, oe# reset timings during embedded algorithms reset# t rp t rb figure 16. reset timings
46 am29lv640mt/b june 12, 2003 advance information ac characteristics erase and program operations notes: 1. not 100% tested. 2. see the ?erase and programming 32-byte performance? section for more information. 3. for 1?16 words/ 1?32 bytes programmed. 4. effective write buffer specification is bas ed upon a 16-word/ 32-byte write buffer operation. 5. word/byte programming specification is based upon a single word/byte programming operation not utilizing the write buffer. parameter speed options jedec std. description 90r 100, 100r 112, 112r 120, 120r unit t avav t wc write cycle time (note 1) min 90 100 110 120 ns t avwl t as address setup time min 0 ns t aso address setup time to oe# low during toggle bit polling min 15 ns t wlax t ah address hold time min 45 ns t aht address hold time from ce# or oe# high during toggle bit polling min 0 ns t dvwh t ds data setup time min 45 ns t whdx t dh data hold time min 0 ns t oeph output enable high during toggle bit polling min 20 ns t ghwl t ghwl read recovery time before write (oe# high to we# low) min 0 ns t elwl t cs ce# setup time min 0 ns t wheh t ch ce# hold time min 0 ns t wlwh t wp write pulse width min 35 ns t whdl t wph write pulse width high min 30 ns t whwh1 t whwh1 write buffer program operation (notes 2, 3) typ 352 s effective write buffer program operation (notes 2, 4) per byte typ 11 s per word typ 22 s accelerated effective write buffer program operation (notes 2, 4) per byte typ 8.8 s per word typ 17.6 s single word/byte program operation (note 2, 5) byte typ 100 s word 100 accelerated single word/byte programming operation (note 2, 5) byte typ 90 s word 90 t whwh2 t whwh2 sector erase operation (note 2) typ 0.5 sec t vhh v hh rise and fall time (note 1) min 250 ns t vcs v cc setup time (note 1) min 50 s t busy we# high to ry/by# low min 90 100 110 120 ns
june 12, 2003 am29lv640mt/b 47 advance information ac characteristics oe# we# ce# v cc data addresses t ds t ah t dh t wp pd t whwh1 t wc t as t wph t vcs 555h pa pa read status data (last two cycles) a0h t cs status d out program command sequence (last two cycles) t ch pa t busy ry/by# n otes: 1 . pa = program address, pd = program data, d out is the true data at the program address. 2 . illustration shows device in word mode. figure 17. program operation timings acc t vhh v hh v il or v ih v il or v ih t vhh figure 18. accelerated program timing diagram
48 am29lv640mt/b june 12, 2003 advance information ac characteristics oe# ce# addresses v cc we# data 2aah sa t ah t wp t wc t as t wph 555h for chip erase 10 for chip erase 30h t ds t vcs t cs t dh 55h t ch in progress complete t whwh2 va va erase command sequence (last two cycles) read status data ry/by# t rb t busy notes: 1. sa = sector address (for sector erase), va = valid address for reading status data (see ?write operation status?. 2. these waveforms are for the word mode. figure 19. chip/sector erase operation timings
june 12, 2003 am29lv640mt/b 49 advance information ac characteristics we# ce# oe# high z t oe high z dq7 dq0?dq6 ry/by# t busy complement true addresses va t oeh t ce t ch t oh t df va va status data complement status data true valid data valid data t acc t rc note: va = valid address. illustration shows first status cycle after command sequence, last status read cycle, and array data read cycle. figure 20. data# polling timings (during embedded algorithms)
50 am29lv640mt/b june 12, 2003 advance information ac characteristics oe# ce# we# addresses t oeh t dh t aht t aso t oeph t oe valid data (first read) (second read) (stops toggling) t ceph t aht t as dq6/dq2 valid data valid status valid status valid status ry/by# note: va = valid address; not required for dq6. illustration shows first two status cycle after command sequence, last status read cycle, and array data read cycle figure 21. toggle bit timings (d uring embedded algorithms) note: dq2 toggles only when read at an address within an erase-suspended sector. the system may use oe# or ce# to toggle dq2 and dq6. figure 22. dq2 vs. dq6 enter erase erase erase enter erase suspend program erase suspend read erase suspend read erase we# dq6 dq2 erase complete erase suspend suspend program resume embedded erasing
june 12, 2003 am29lv640mt/b 51 advance information ac characteristics temporary sector unprotect note: not 100% tested. parameter all speed options jedec std description unit t vidr v id rise and fall time (see note) min 500 ns t rsp reset# setup time for temporary sector unprotect min 4 s reset# t vidr v id v ss , v il , or v ih v id v ss , v il , or v ih ce# we# ry/by# t vidr t rsp program or erase command sequence t rrb figure 23. temporary sector group unprotect timing diagram
52 am29lv640mt/b june 12, 2003 advance information ac characteristics sector group prote ct: 150 s, sector group unprote ct: 15 ms 1 s reset# sa, a6, a1, a0 data ce# we# oe# 60h 60h 40h valid* valid* valid* status sector group protect or unprotect verify v id v ih * for sector group protect, a6?a0 = 0xx0010. for sector group unprotect, a6?a0 = 1xx0010. figure 24. sector group protect and unprotect timing diagram
june 12, 2003 am29lv640mt/b 53 advance information ac characteristics alternate ce# controlled er ase and program operations notes: 1. not 100% tested. 2. see the ?erase and programming performance? section for more information. 3. for 1?16 words programmed/1?32 bytes programmed. 4. effective write buffer specification is bas ed upon a 16-word/32-byte write buffer operation. 5. word/byte programming specification is based upon a single word/byte programming operation not utilizing the write buffer. parameter description speed options jedec std. 90r 100, 100r 112, 112r 120, 120r unit t avav t wc write cycle time (note 1) min 90 100 110 120 ns t avwl t as address setup time min 0 ns t elax t ah address hold time min 45 ns t dveh t ds data setup time min 45 ns t ehdx t dh data hold time min 0 ns t ghel t ghel read recovery time before write (oe# high to we# low) min 0 ns t wlel t ws we# setup time min 0 ns t ehwh t wh we# hold time min 0 ns t eleh t cp ce# pulse width min 45 ns t ehel t cph ce# pulse width high min 30 ns t whwh1 t whwh1 write buffer program operation (notes 2, 3) typ 352 s effective write buffer program operation (notes 2, 4) per byte typ 11 s per word typ 22 s accelerated effective write buffer program operation (notes 2, 4) per byte typ 8.8 s per word typ 17.6 s single word/byte program operation (note 2) byte typ 100 s word 100 accelerated single word/byte programming operation (note 2) byte typ 90 s word 90 t whwh2 t whwh2 sector erase operation (note 2) typ 0.5 sec t rh reset high time before write (note 1) min 50 ns
54 am29lv640mt/b june 12, 2003 advance information ac characteristics t ghel t ws oe# ce# we# reset# t ds data t ah addresses t dh t cp dq7# d out t wc t as t cph pa data# polling a0 for program 55 for erase t rh t whwh1 or 2 ry/by# t wh pd for program 30 for sector erase 10 for chip erase 555 for program 2aa for erase pa for program sa for sector erase 555 for chip erase t busy notes: 1. figure indicates last two bus cycles of a program or erase operation. 2. pa = program address, sa = sector address, pd = program data. 3. dq7# is the complement of the data written to the device. d out is the data written to the device. 4. waveforms are for the word mode. figure 25. alternate ce# controlled write (erase/program) operation timings
june 12, 2003 am29lv640mt/b 55 advance information erase and programming performance notes: 1. typical program and erase times assume the following conditions: 25 c, 3.0 v v cc . programming specifications assume that all bits are programmed to 00h. 2. maximum values are measured at v cc = 3.0 v, worst case temperature. maximum values are valid up to and including 100,000 program/erase cycles. 3. word/byte programming specification is based upon a single word/byte programming operation not utilizing the write buffer. 4. for 1-16 words or 1-32 bytes programmed ina single write buffer programming operation. 5. effective write buffer specification is calculated on a per-w ord/per-byte basis for a 16-word/32-byte write buffer operation. 6. in the pre-programming step of the embedded erase algorithm, all bits are programmed to 00h before erasure. 7. system-level overhead is the time required to execute t he command sequence(s) for the program command. see tables 12 and 11 for further information on command definitions. 8. the device has a minimum erase and program cycle endurance of 100,000 cycles. latchup characteristics note: includes all pins except v cc . test conditions: v cc = 3.0 v, one pin at a time. tsop pin and bga package capacitance notes: 1. sampled, not 100% tested. 2. test conditions t a = 25c, f = 1.0 mhz. parameter typ (note 1) max (note 2) unit comments sector erase time 0.5 15 sec chip erase time 32 128 sec single word/byte program time (note 3) byte 100 tbd s word 100 tbd s accelerated single word/byte program time (note 3) byte 90 tbd s word 90 tbd s total write buffer program time (note 4) 352 tbd s effective write buffer program time (note 5) per byte 11 tbd s per word 22 tbd s total accelerated effective write buffer program time (note 4) 282 tbd s effective accelerated write buffer program time (note 4) byte 8.8 tbd s description min max input voltage with respect to v ss on all pins except i/o pins (including a9, oe#, and reset#) ?1.0 v 12.5 v input voltage with respect to v ss on all i/o pins ?1.0 v v cc + 1.0 v v cc current ?100 ma +100 ma parameter symbol parameter description test setup typ max unit c in input capacitance v in = 0 tsop 6 7.5 pf fine-pitch bga 4.2 5.0 pf c out output capacitance v out = 0 tsop 8.5 12 pf fine-pitch bga 5.4 6.5 pf c in2 control pin capacitance v in = 0 tsop 7.5 9 pf fine-pitch bga 3.9 4.7 pf
56 am29lv640mt/b june 12, 2003 advance information data retention parameter description test conditions min unit minimum pattern data retention time 150 c10years 125 c20years
june 12, 2003 am29lv640mt/b 57 advance information physical dimensions ts 048?48-pin standard pinout th in small outline package (tsop) dwg rev aa; 10/99
58 am29lv640mt/b june 12, 2003 advance information physical dimensions fbe063?63-ball fine-pitch ball grid array ( f bga) 12 x 11 mm package dwg rev af; 10/99
june 12, 2003 am29lv640mt/b 59 advance information physical dimensions laa064?64-ball fortified ball grid array ( f bga) 13 x 11 mm package
60 am29lv640mt/b june 12, 2003 advance information revision summary revision a (april 26, 2002) initial release. revision b (may 23, 2002) changed packaging from 64-ball fbga to 64-ball for- tified bga. changed block diagram: moved v io from ry/by# to input/output buffers. changed note about wp#/acc pin to indicate internal pullup to v cc . revision b+1 (july 31, 2002) mirrorbit 64 mbit device family added 64 fortified bga to lv640mu device. alternate ce# controlled erase and program operations added t rh parameter to table. erase and program operations added t busy parameter to table. figure 16. program operation timings added ry/by# to waveform. tsop and bga pin capacitance added the fbga package. program suspend/program resume command sequence changed 15 s typical to maximum and added 5 s typical. erase suspend/erase resume commands changed typical from 20 s to 5 s and added a maxi- mum of 20 s. revision b+2 (august 9, 2002) valid combinations for tsop package added 100r, 110r, and 120r opns. valid combinations for bga package added 100r, 110r, and 120r opns. cmos compatible added note 8. special package handling instructions modified the special handling wording. dc characteristics table deleted the i acc specification row. cfi changed text in the third paragraph of cfi to read ?reading array data.? revision b+3 (september 19, 2002) ordering information deleted fi from valid combinations table. revision b+4 (october 15, 2002) connection diagrams changed from 56-pin standard tsop to 48-pin stan- dard tsop. product selector guide added regulated opns. revision c (december 5, 2002) secsi sector flash memory region, and enter secsi sector/exit secsi sector command sequence noted that the a cc function and unlock bypass modes are not available when the secsi sector is enabled. byte/word program command sequence, sector erase command sequence, and chip erase com- mand sequence noted that the secsi sector, autoselect, and cfi func- tions are unavailable when a program or erase opera- tion is in progress. common flash memory interface (cfi) changed cfi website address. command definitions changed wording in last sentence of first paragraph from, ?...resets the device to reading array data.? to ...?may place the device to an unknown state. a reset command is then required to return the device to read- ing array data.? cmos compatible added i lr parameter to table. removed v il , v ih , v ol , and v oh from table and added v il1 , v ih1 , v il2 , v ih2 , v ol , v oh1 , and v oh2 from the cmos table in the am29lv640mh/l datasheet. changed v ih1 and v ih2 minimum to 1.9. removed typos in notes.
ac characteristics and read-only operations changed the chip enable to output high z and out- put enable to output high z speed options from 30 ns to 16 ns. word/byte configuration changed byte# switching low to output high z speed options from 30 ns to 16 ns. customer lockable: secsi sector not programmed or protected at the factory. added second bullet, secsi sector-protect. revision c+1 (february 16, 2003) distinctive characteristics corrected performance characteristics. product selector guide added note 2. connection diagrams changed pin f1 to nc. ordering information corrected valid combinations table. added note. ac characteristics removed 93, 93r speed option. added note input values in the t whwh 1 and t whwh 2 parameters in the erase and program options table that were previ- ously tbd. also, added note 5. input values in the t whwh 1 and t whwh 2 parameters in the alternate ce# controlled erase and program op- tions table that were previously tbd. also, added note 5. erase and programming performance input values into table that were previously tbd. added note 3 and 4 revision c+2 (june 12, 2003) ordering information added 90r speed grade. erase and programming performance modified table and notes, inserted values for typical. trademarks copyright ? 2003 advanced micro devices, inc. all rights reserved. amd, the amd logo, and combinations thereof are regi stered trademarks of advanced micro devices, inc. expressflash is a trademark of advanced micro devices, inc. product names used in this publication ar e for identification purposes only and may be trademarks of their respective companies .
62 am29lv640mt/b june 12, 2003 advance information ?2003 advanced micro devices, inc . 01/03 printed in usa one amd place, p.o. box 3453, sunnyvale, ca 94088-3453 408-732-2400 twx 910-339-9280 telex 34-6306 800-538-8450 http://www.amd.com advanced micro devices reserves the right to make changes in its product without notice in order to impr ove design or performance characteristics.the performance characteristics listed in this document are guaranteed by specific tests, guard banding, design and other practices common to the industry. for specific testing details, contact your local amd sales representativ e.the company assumes no responsibility for the use of any circuits described herein. ? advanced micro devices, inc. all rights reser ved. amd, the amd arrow logo and combination thereof, are trademarks of advanced micro devices, inc. other product names are for informational purposes only and may be trademarks of their respective companies. north america alabama . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 256)830-9192 arizona . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 602)242-4400 california, irvine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(949)450-7500 sunnyvale . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 408)732-2400 colorado . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 303)741-2900 connecticut . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 203)264-7800 florida, clearwater . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(727)793-0055 miami (lakes) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(305)820-1113 georgia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 770)814-0224 illinois, chicago . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(630)773-4422 massachusetts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 7 8 1 ) 2 1 3 - 6400 michigan . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(248)471-6294 minnesota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 6 1 2 ) 74 5 - 0005 new jersey, chatham . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 9 7 3 ) 7 0 1-1777 new york . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 7 1 6 ) 4 2 5 - 8050 north carolina . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(919)840-8080 oregon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 503)245-0080 pennsylvania . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 2 1 5 ) 340-1187 south dakota . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 605)692-5777 texas, austin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 5 1 2 ) 346-7830 dallas . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(972)985-1344 houston . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(281)376-8084 virginia . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(703)736-9568 international australia, north ryde . . . . . . . . . . . . . . . . . . . . . . . tel(61)2-88-777-222 belgium, antwerpen . . . . . . . . . . . . . . . . . . . . . . . . tel(32)3-248-43-00 brazil, san paulo . . . . . . . . . . . . . . . . . . . . . . . . . . tel(55)11-5501-2105 china, beijing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(86)10-6510-2188 shanghai . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(86)21-635-00838 shenzhen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(86)755-246-1550 finland, helsinki . . . . . . . . . . . . . . . . . . . . . . tel(358)881-3117 france, paris . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(33)-1-49751010 germany, bad homburg . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(49)-6172- 92670 munich . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(49)-89-450530 hong kong, causeway bay . . . . . . . . . . . . . . . . . . . tel(85)2-2956-0388 italy,milan . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(39)-02-381961 india,new delhi . . . . . . . . . . . . . . . . . . . . . . . . . .tel(91)11-623-8620 japan, osaka . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(81)6-6243-3250 tokyo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(81)3-3346-7600 korea, seoul . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(82)2-3468-2600 russia, moscow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(7)-095-795-06-22 sweden, stockholm . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(46)8-562-540-00 taiwan,taipei . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(886)2-8773-1555 united kingdom, frimley . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .tel(44)1276-803100 haydock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . tel(44)1942-272888 representatives in u.s. and canada arizona, tempe - centaur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 480)839-2320 california, calabasas - centaur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 8 1 8 ) 878-5800 irvine - centaur . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 9 4 9 ) 2 6 1 - 2 1 2 3 san diego - centaur. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 858)278-4950 santa clara - fourfront. . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 408)350-4800 canada, burnaby, b.c. - davetek marketing. . . . . . . . . . . . . . . . . . . . ( 604)430-3680 calgary, alberta - davetek marketing. . . . . . . . . . . . . . . . . ( 403)283-3577 kanata, ontario - j-squared tech. . . . . . . . . . . . . . . . . . . . ( 6 1 3 ) 5 9 2 - 9 5 4 0 mississauga, ontario - j-squared tech. . . . . . . . . . . . . . . . . . ( 905)672-2030 st laurent, quebec - j-squared tech. . . . . . . . . . . . . . . . ( 5 1 4 ) 7 4 7 - 1 2 1 1 colorado, golden - compass marketing . . . . . . . . . . . . . . . . . . . . . . ( 303)277-0456 florida, melbourne - marathon technical sales . . . . . . . . . . . . . . . . ( 3 2 1 ) 7 2 8 - 7706 ft. lauderdale - marathon technical sales . . . . . . . . . . . . . . ( 954)527-4949 orlando - marathon technical sales . . . . . . . . . . . . . . . . . . ( 407)872-5775 st. petersburg - marathon technical sales . . . . . . . . . . . . . . ( 7 2 7 ) 8 9 4 - 3603 georgia, duluth - quantum marketing . . . . . . . . . . . . . . . . . . . . .(678)584-1128 illinois, skokie - industrial reps, inc. . . . . . . . . . . . . . . . . . . . . . . . . ( 8 4 7 ) 9 6 7 - 8430 indiana, kokomo - sai . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ( 7 6 5 ) 4 5 7 - 7 2 4 1 iowa, cedar rapids - lorenz sales . . . . . . . . . . . . . . . . . . . . . . ( 3 1 9 ) 2 9 4 - 1 0 0 0 kansas, lenexa - lorenz sales . . . . . . . . . . . . . . . . . . . . . . . . . ( 9 13)469-1312 massachusetts, burlington - synergy associates . . . . . . . . . . . . . . . . . . . . . ( 7 8 1 ) 238-0870 michigan, brighton - sai . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(810)227-0007 minnesota, st. paul - cahill, schmitz & cahill, inc. . . . . . . . . . . . . . . . . . ( 6 5 1 ) 69 9 - 0200 missouri, st. louis - lorenz sales . . . . . . . . . . . . . . . . . . . . . . . . . . (314)997-4558 new jersey, mt. laurel - sj associates . . . . . . . . . . . . . . . . . . . . . . . . . ( 8 5 6 ) 866-1234 new york, buffalo - nycom, inc. . . . . . . . . . . . . . . . . . . . . . . . . .(716)741-7116 east syracuse - nycom, inc. . . . . . . . . . . . . . . . . . . . . . . ( 3 1 5 ) 437-8343 pittsford - nycom, inc. . . . . . . . . . . . . . . . . . . . . . . . . . . ( 7 1 6 ) 586-3660 rockville centre - sj associates . . . . . . . . . . . . . . . . . . . . ( 5 1 6 ) 536-4242 north carolina, raleigh - quantum marketing . . . . . . . . . . . . . . . . . . . . . .(919)846-5728 ohio, middleburg hts - dolfuss root & co. . . . . . . . . . . . . . . . . ( 440)816-1660 powell - dolfuss root & co. . . . . . . . . . . . . . . . . . . . . . . ( 6 1 4 ) 7 8 1 - 0 7 2 5 vandalia - dolfuss root & co. . . . . . . . . . . . . . . . . . . . . .(937)898-9610 westerville - dolfuss root & co. . . . . . . . . . . . . . . . . . . ( 6 1 4 ) 5 2 3 -1990 oregon, lake oswego - i squared, inc. . . . . . . . . . . . . . . . . . . . . . . ( 503)670-0557 utah, murray - front range marketing . . . . . . . . . . . . . . . . . . . . ( 8 0 1 ) 288-2500 virginia, glen burnie - coherent solution, inc. . . . . . . . . . . . . . . . . ( 4 1 0 ) 7 6 1 - 2 2 5 5 washington, kirkland - i squar ed,inc. . . . . . . . . . . . . . . . . . . . . . . . . . .(425)822-9220 wisconsin, pewaukee - industrial representatives . . . . . . . . . . . . . . . . ( 2 6 2 ) 5 74 - 9 3 9 3 representatives in latin america argentina, capital f ederal argentina/ww rep. . . . . . . . . . . . . . . . . . . .54 -11)4373-0655 chile, santiago - latinrep/wwrep. . . . . . . . . . . . . . . . . . . . . . . . . .(+562)264-0993 columbia, bogota - dimser. . . . . . . . . . . . . . . . . . . . . . . . . . . . . .(571)410-4182 mexico, guadalajara - latinrep/ww rep. . . . . . . . . . . . . . . . . . . . ( 5 2 3 ) 8 1 7 - 3900 mexico city - latinrep/ww rep. . . . . . . . . . . . . . . . . . . . ( 5 2 5 ) 7 5 2 - 2727 monterrey - latinrep/ww rep. . . . . . . . . . . . . . . . . . . . .(528)369-6828 puert o rico, boqueron - infitronics. . . . . . . . . . . . . . . . . . . . . . . . . . . . (787)851-6000 sales offices and representatives es

▲Up To Search▲

Price & Availability of AM29LV640MTB

	To Download AM29LV640MTB Datasheet File
If you can't view the Datasheet, Please click here to try to view without PDF Reader .